[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iKCGPM03L2dE60VWOfYwbiHj1vRAXvqZuts0Ce-VdpifQ@mail.gmail.com>
Date: Tue, 18 Jun 2019 11:19:11 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
netdev <netdev@...r.kernel.org>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Jason Baron <jbaron@...mai.com>,
Christoph Paasch <cpaasch@...le.com>,
David Laight <David.Laight@...lab.com>,
Yuchung Cheng <ycheng@...gle.com>
Subject: Re: [PATCH 1/2] net: fastopen: make key handling more robust against
future changes
On Tue, Jun 18, 2019 at 11:18 AM Eric Biggers <ebiggers@...nel.org> wrote:
> The length parameter makes no sense if it's not checked, though. Either it
> should exist and be checked, or it should be removed and the length should be
> implicitly TCP_FASTOPEN_KEY_LENGTH.
Sure, please send a patch.
Powered by blists - more mailing lists