From: Eric Dumazet <eric.dumazet@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH net-next 0/2] tcp: RFC 6056 induced changes
Date: Tue, 9 Feb 2021 11:20:26 -0800 [thread overview]
Message-ID: <20210209192028.3350290-1-eric.dumazet@gmail.com> (raw)
From: Eric Dumazet <edumazet@google.com>
This is based on a report from David Dworken.
First patch implements RFC 6056 3.3.4 proposal.
Second patch is adding a little bit of noise to make
attacker life a bit harder.
Eric Dumazet (2):
tcp: change source port randomizarion at connect() time
tcp: add some entropy in __inet_hash_connect()
net/ipv4/inet_hashtables.c | 25 ++++++++++++++++++++++---
1 file changed, 22 insertions(+), 3 deletions(-)
--
2.30.0.478.g8a0d178c01-goog
next reply other threads:[~2021-02-09 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 19:20 Eric Dumazet [this message]
2021-02-09 19:20 ` [PATCH net-next 1/2] tcp: change source port randomizarion at connect() time Eric Dumazet
2021-02-09 19:20 ` [PATCH net-next 2/2] tcp: add some entropy in __inet_hash_connect() Eric Dumazet
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=20210209192028.3350290-1-eric.dumazet@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).