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
| ||
|
Message-ID: <20170504134357.GA25251@bistromath.localdomain> Date: Thu, 4 May 2017 15:43:57 +0200 From: Sabrina Dubroca <sd@...asysnail.net> To: Steffen Klassert <steffen.klassert@...unet.com> Cc: netdev@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au> Subject: Re: [PATCH net] ah: use crypto_memneq to check the ICV 2017-05-04, 12:41:24 +0200, Steffen Klassert wrote: > On Wed, May 03, 2017 at 04:57:57PM +0200, Sabrina Dubroca wrote: > > Signed-off-by: Sabrina Dubroca <sd@...asysnail.net> > > --- > > net/ipv4/ah4.c | 5 +++-- > > net/ipv6/ah6.c | 5 +++-- > > 2 files changed, 6 insertions(+), 4 deletions(-) > > Is this a fix for something? If so, please describe what it fixes. > If not, it can wait until after the merge window and merged into > ipsec-next then. Yeah, not really. I suppose you could see it as a fix for the commit that introduced crypto_memneq and did some conversions (6bf37e5aa90f ("crypto: crypto_memneq - add equality testing of memory regions w/o timing leaks")), but that may be a bit of a stretch. I can repost that for ipsec-next in a couple of weeks. Thanks, -- Sabrina
Powered by blists - more mailing lists