diff options
| author |   Dmitry Safonov <dima@arista.com> | 2023-10-23 20:21:56 +0100 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2023-10-27 10:35:44 +0100 |
| commit | 0aadc73995d08f6b0dc061c14a564ffa46f5914e (patch) | |
| tree | d104c5c1772bec3362f2aababc1b5a79ec3e44bc /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | net/tcp: Introduce TCP_AO setsockopt()s (diff) | |
| download | wireguard-linux-0aadc73995d08f6b0dc061c14a564ffa46f5914e.tar.xz wireguard-linux-0aadc73995d08f6b0dc061c14a564ffa46f5914e.zip | |
net/tcp: Prevent TCP-MD5 with TCP-AO being set
Be as conservative as possible: if there is TCP-MD5 key for a given peer
regardless of L3 interface - don't allow setting TCP-AO key for the same
peer. According to RFC5925, TCP-AO is supposed to replace TCP-MD5 and
there can't be any switch between both on any connected tuple.
Later it can be relaxed, if there's a use, but in the beginning restrict
any intersection.
Note: it's still should be possible to set both TCP-MD5 and TCP-AO keys
on a listening socket for *different* peers.
Co-developed-by: Francesco Ruggeri <fruggeri@arista.com>
Signed-off-by: Francesco Ruggeri <fruggeri@arista.com>
Co-developed-by: Salam Noureddine <noureddine@arista.com>
Signed-off-by: Salam Noureddine <noureddine@arista.com>
Signed-off-by: Dmitry Safonov <dima@arista.com>
Acked-by: David Ahern <dsahern@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions