| 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: <20141125145850.GD8541@gondor.apana.org.au> Date: Tue, 25 Nov 2014 22:58:50 +0800 From: Herbert Xu <herbert@...dor.apana.org.au> To: Stephan Mueller <smueller@...onox.de> Cc: Daniel Borkmann <dborkman@...hat.com>, 'Quentin Gouchet' <quentin.gouchet@...il.com>, lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-crypto@...r.kernel.org, linux-api@...r.kernel.org Subject: Re: [PATCH v3 4/7] crypto: AF_ALG: add AEAD support On Mon, Nov 24, 2014 at 03:58:34PM +0100, Stephan Mueller wrote: > Ok. But in the code you see that skcipher is a 100% subset of AEAD. For > AEAD, all we need to do in addition to normal symmetric ciphers is to > select the AEAD kernel crypto API calls, to locate and use the AD and to > ensure we have the right memory size to process the tag. There is still one fundamental difference between AEAD and ciphers. Namely that ciphers can operate as you go while AEAD requests must be done in one lot. So that should make the AEAD code simpler vs. ciphers. I think the best course of action for now is to start with sharing no code and then chop bits off as we see fit. Cheers, -- Email: Herbert Xu <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists