| 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
| ||
|
Date: Tue, 25 Nov 2014 16:08:35 +0100 From: Stephan Mueller <smueller@...onox.de> To: Herbert Xu <herbert@...dor.apana.org.au> 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 Am Dienstag, 25. November 2014, 22:58:50 schrieb Herbert Xu: Hi Herbert, >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. Yes, that is a key difference. > >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. Ok, I will create a new patch set with a separate algif_aead.c. I guess the entire sgl handling logic will be gone in AEAD. > >Cheers, Ciao Stephan -- 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