diff options
author | KOVACS Krisztian <hidden@balabit.com> | 2016-09-23 09:27:42 (GMT) |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2016-09-25 21:16:11 (GMT) |
commit | 7a682575ad4829b4de3e672a6ad5f73a05826b82 (patch) | |
tree | b6cfa1d00df267b3ffadbfd7d513a5695c619ce4 /include/crypto/null.h | |
parent | 58e207e4983d7acea39b7fbec9343d8a6d218a18 (diff) | |
download | linux-7a682575ad4829b4de3e672a6ad5f73a05826b82.tar.xz |
netfilter: xt_socket: fix transparent match for IPv6 request sockets
The introduction of TCP_NEW_SYN_RECV state, and the addition of request
sockets to the ehash table seems to have broken the --transparent option
of the socket match for IPv6 (around commit a9407000).
Now that the socket lookup finds the TCP_NEW_SYN_RECV socket instead of the
listener, the --transparent option tries to match on the no_srccheck flag
of the request socket.
Unfortunately, that flag was only set for IPv4 sockets in tcp_v4_init_req()
by copying the transparent flag of the listener socket. This effectively
causes '-m socket --transparent' not match on the ACK packet sent by the
client in a TCP handshake.
Based on the suggestion from Eric Dumazet, this change moves the code
initializing no_srccheck to tcp_conn_request(), rendering the above
scenario working again.
Fixes: a940700003 ("netfilter: xt_socket: prepare for TCP_NEW_SYN_RECV support")
Signed-off-by: Alex Badics <alex.badics@balabit.com>
Signed-off-by: KOVACS Krisztian <hidden@balabit.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'include/crypto/null.h')
0 files changed, 0 insertions, 0 deletions