summaryrefslogtreecommitdiff
path: root/net/llc/Kconfig
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2017-05-05 16:56:54 +0300
committerDavid S. Miller <davem@davemloft.net>2017-05-05 19:00:11 +0300
commit84b114b98452c431299d99c135f751659e517acb (patch)
tree53778bfd4964bed65ac40a9c1c57a73f21cb9664 /net/llc/Kconfig
parent9051247dcf9ecee156d2ddac39a4f1ca591f8428 (diff)
downloadlinux-84b114b98452c431299d99c135f751659e517acb.tar.xz
tcp: randomize timestamps on syncookies
Whole point of randomization was to hide server uptime, but an attacker can simply start a syn flood and TCP generates 'old style' timestamps, directly revealing server jiffies value. Also, TSval sent by the server to a particular remote address vary depending on syncookies being sent or not, potentially triggering PAWS drops for innocent clients. Lets implement proper randomization, including for SYNcookies. Also we do not need to export sysctl_tcp_timestamps, since it is not used from a module. In v2, I added Florian feedback and contribution, adding tsoff to tcp_get_cookie_sock(). v3 removed one unused variable in tcp_v4_connect() as Florian spotted. Fixes: 95a22caee396c ("tcp: randomize tcp timestamp offsets for each connection") Signed-off-by: Eric Dumazet <edumazet@google.com> Reviewed-by: Florian Westphal <fw@strlen.de> Tested-by: Florian Westphal <fw@strlen.de> Cc: Yuchung Cheng <ycheng@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/llc/Kconfig')
0 files changed, 0 insertions, 0 deletions