netdev - Re: crypto: skcipher - Use eseqiv even on UP machines

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20131025065049.GB31491@secunet.com>
Date:	Fri, 25 Oct 2013 08:50:49 +0200
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: crypto: skcipher - Use eseqiv even on UP machines

On Thu, Oct 24, 2013 at 08:41:49PM +0800, Herbert Xu wrote:
> Hi:
>     
> Previously we would use eseqiv on all async ciphers in all cases,
> and sync ciphers if we have more than one CPU.  This meant that
> chainiv is only used in the case of sync ciphers on a UP machine.
> 
> As chainiv may aid attackers by making the IV predictable, even
> though this risk itself is small, the above usage pattern causes
> it to further leak information about the host.
> 
> This patch addresses these issues by using eseqiv even if we're
> on a UP machine.
> 
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>
> 

That's fine by me.

Acked-by: Steffen Klassert <steffen.klassert@...unet.com>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html