From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: calvinowens@fb.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
edumazet@google.com, kernel-team@fb.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp: Restore RFC5961-compliant behavior for SYN packets
Date: Fri, 21 Nov 2014 15:34:38 -0500 (EST) [thread overview]
Message-ID: <20141121.153438.43820255874630231.davem@davemloft.net> (raw)
In-Reply-To: <1416536527.8629.74.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 20 Nov 2014 18:22:07 -0800
> On Thu, 2014-11-20 at 17:47 -0800, Calvin Owens wrote:
>
>> That's actually not what led to finding this, but it's a good point. :)
>>
>> What if the challenge-ACK counter were decremented in tcp_validate_incoming()
>> when a valid RST packet is seen? That would allow legitimate remote
>> hosts to reestablish connections without being ratelimited, and still
>> prevent a malicious host from guessing sequence numbers.
>>
>> There would need to be a way to tell if a challenge ACK had in fact been
>> sent and only decrement in that case, since otherwise a local attacker
>> could establish and immediately reset lots of connections to keep the
>> counter below the ratelimit threshold and guess sequence numbers.
>>
>> Simply adding a flag to struct tcp_sock would work: just set the flag
>> whenever a challenge ACK is sent, and clear it and decrement the counter
>> only if it is set when a valid RST packet is seen.
>
> Seems tricky, a Challenge ACK do not necessarily gives an RST.
>
> Anyway this certainly can wait, as we already have a sysctl to
> eventually work around the issue.
>
> Acked-by: Eric Dumazet <edumazet@google.com>
Applied, thanks everyone.
next prev parent reply other threads:[~2014-11-21 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 23:09 Calvin Owens
2014-11-20 23:42 ` Eric Dumazet
2014-11-21 1:47 ` Calvin Owens
2014-11-21 2:22 ` Eric Dumazet
2014-11-21 20:34 ` David Miller [this message]
2014-11-21 18:55 ` Neal Cardwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141121.153438.43820255874630231.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=calvinowens@fb.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=kernel-team@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®