Re: [PATCH net] tcp md5sig: Use skb's saddr when replying to an incoming segment

2017-12-12 Thread David Miller
From: Christoph Paasch Date: Mon, 11 Dec 2017 00:05:46 -0800 > The MD5-key that belongs to a connection is identified by the peer's > IP-address. When we are in tcp_v4(6)_reqsk_send_ack(), we are replying > to an incoming segment from tcp_check_req() that failed the seq-number > checks. > > Thus

Re: [PATCH net] tcp md5sig: Use skb's saddr when replying to an incoming segment

2017-12-11 Thread Eric Dumazet
On Mon, 2017-12-11 at 00:05 -0800, Christoph Paasch wrote: > The MD5-key that belongs to a connection is identified by the peer's > IP-address. When we are in tcp_v4(6)_reqsk_send_ack(), we are > replying > to an incoming segment from tcp_check_req() that failed the seq- > number > checks. > > Thu

[PATCH net] tcp md5sig: Use skb's saddr when replying to an incoming segment

2017-12-11 Thread Christoph Paasch
The MD5-key that belongs to a connection is identified by the peer's IP-address. When we are in tcp_v4(6)_reqsk_send_ack(), we are replying to an incoming segment from tcp_check_req() that failed the seq-number checks. Thus, to find the correct key, we need to use the skb's saddr and not the daddr