netdev - Re: [PATCH v3 00/36] net/tcp: Add TCP-AO support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c0b6c5f1-9b4f-2d3d-69fd-533daa023e09@kernel.org>
Date:   Mon, 31 Oct 2022 20:22:41 -0600
From:   David Ahern <dsahern@...nel.org>
To:     Dmitry Safonov <dima@...sta.com>, linux-kernel@...r.kernel.org,
        Eric Dumazet <edumazet@...gle.com>
Cc:     Andy Lutomirski <luto@...capital.net>,
        Ard Biesheuvel <ardb@...nel.org>,
        Bob Gilligan <gilligan@...sta.com>,
        Dan Carpenter <dan.carpenter@...cle.com>,
        "David S. Miller" <davem@...emloft.net>,
        Dmitry Safonov <0x7f454c46@...il.com>,
        Eric Biggers <ebiggers@...nel.org>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        Francesco Ruggeri <fruggeri@...sta.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
        Ivan Delalande <colona@...sta.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Leonard Crestez <cdleonard@...il.com>,
        Paolo Abeni <pabeni@...hat.com>,
        Salam Noureddine <noureddine@...sta.com>,
        Shuah Khan <shuah@...nel.org>, netdev@...r.kernel.org,
        linux-crypto@...r.kernel.org
Subject: Re: [PATCH v3 00/36] net/tcp: Add TCP-AO support

Thinking about how to move the TCP-AO intent forward: clearly a 36-patch
set is a bit much. The first 6 patches are prep work, and we know there
is a use case for those.

We could handle patches 3 and 4 as a stand alone set first.

Once merged, deal with the crypto API and users until those maintainers
are good. That would be patches 1, 2, 5 and 6.

Once those are merged it drops down to just networking patches with
selftests. Those can be split into AO (19) and selftests (11) making it
4 total sets of manageable size.

The AO patches can be reviewed until convergence on a good starting point.

Sound reasonable?