From: patchwork-bot+netdevbpf@kernel.org
To: Willy Tarreau <w@1wt.eu>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, moshe.kol@mail.huji.ac.il,
yossi.gilad@mail.huji.ac.il, aksecurity@gmail.com,
Jason@zx2c4.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net 0/7] insufficient TCP source port randomness
Date: Thu, 05 May 2022 02:50:14 +0000 [thread overview]
Message-ID: <165171901434.9346.11862672519464851497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220502084614.24123-1-w@1wt.eu>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 May 2022 10:46:07 +0200 you wrote:
> Hi,
>
> In a not-yet published paper, Moshe Kol, Amit Klein, and Yossi Gilad
> report being able to accurately identify a client by forcing it to emit
> only 40 times more connections than the number of entries in the
> table_perturb[] table, which is indexed by hashing the connection tuple.
> The current 2^8 setting allows them to perform that attack with only 10k
> connections, which is not hard to achieve in a few seconds.
>
> [...]
Here is the summary with links:
- [v3,net,1/7] secure_seq: use the 64 bits of the siphash for port offset calculation
https://git.kernel.org/netdev/net/c/b2d057560b81
- [v3,net,2/7] tcp: use different parts of the port_offset for index and offset
https://git.kernel.org/netdev/net/c/9e9b70ae923b
- [v3,net,3/7] tcp: resalt the secret every 10 seconds
https://git.kernel.org/netdev/net/c/4dfa9b438ee3
- [v3,net,4/7] tcp: add small random increments to the source port
https://git.kernel.org/netdev/net/c/ca7af0402550
- [v3,net,5/7] tcp: dynamically allocate the perturb table used by source ports
https://git.kernel.org/netdev/net/c/e9261476184b
- [v3,net,6/7] tcp: increase source port perturb table to 2^16
https://git.kernel.org/netdev/net/c/4c2c8f03a5ab
- [v3,net,7/7] tcp: drop the hash_32() part from the index calculation
https://git.kernel.org/netdev/net/c/e8161345ddbb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-05 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 8:46 [PATCH v3 net 0/7] insufficient TCP source port randomness Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 1/7] secure_seq: use the 64 bits of the siphash for port offset calculation Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 2/7] tcp: use different parts of the port_offset for index and offset Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 3/7] tcp: resalt the secret every 10 seconds Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 4/7] tcp: add small random increments to the source port Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 5/7] tcp: dynamically allocate the perturb table used by source ports Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 6/7] tcp: increase source port perturb table to 2^16 Willy Tarreau
2022-05-02 8:46 ` [PATCH v3 net 7/7] tcp: drop the hash_32() part from the index calculation Willy Tarreau
2022-05-05 2:50 ` patchwork-bot+netdevbpf [this message]
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=165171901434.9346.11862672519464851497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jason@zx2c4.com \
--cc=aksecurity@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe.kol@mail.huji.ac.il \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
--cc=yossi.gilad@mail.huji.ac.il \
/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