You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

David S. Miller 6e5714eaf7 net: Compute protocol sequence numbers and fragment IDs using MD5. ... Computers have become a lot faster since we compromised on the partial MD4 hash which we use currently for performance reasons. MD5 is a much safer choice, and is inline with both RFC1948 and other ISS generators (OpenBSD, Solaris, etc.) Furthermore, only having 24-bits of the sequence number be truly unpredictable is a very serious limitation. So the periodic regeneration and 8-bit counter have been removed. We compute and use a full 32-bit sequence number. For ipv6, DCCP was found to use a 32-bit truncated initial sequence number (it needs 43-bits) and that is fixed here as well. Reported-by: Dan Kaminsky <dan@doxpara.com> Tested-by: Willy Tarreau <w@1wt.eu> Signed-off-by: David S. Miller <davem@davemloft.net>		14 years ago
..
ccids	dccp ccid-2: Perform congestion-window validation	14 years ago
Kconfig	…
Makefile	…
ackvec.c	…
ackvec.h	…
ccid.c	dccp: cosmetics of info message	14 years ago
ccid.h	…
dccp.h	…
diag.c	…
feat.c	…
feat.h	…
input.c	dccp: Clean up slow-path input processing	14 years ago
ipv4.c	net: Compute protocol sequence numbers and fragment IDs using MD5.	14 years ago
ipv6.c	net: Compute protocol sequence numbers and fragment IDs using MD5.	14 years ago
ipv6.h	…
minisocks.c	…
options.c	…
output.c	dccp: combine the functionality of enqeueing and cloning	14 years ago
probe.c	…
proto.c	…
qpolicy.c	…
sysctl.c	…
timer.c	…