| 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: <201101070102.26927.mihai.dontu@gmail.com> Date: Fri, 7 Jan 2011 01:02:25 +0200 From: Mihai Donțu <mihai.dontu@...il.com> To: Pavel Roskin <proski@....org> Cc: Herbert Xu <herbert@...dor.apana.org.au>, Linus Torvalds <torvalds@...ux-foundation.org>, "David S. Miller" <davem@...emloft.net>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Crypto Mailing List <linux-crypto@...r.kernel.org> Subject: Re: Crypto Update for 2.6.38 On Thursday 06 January 2011 23:46:02 Pavel Roskin wrote: > On 01/06/2011 04:16 PM, Herbert Xu wrote: > > This is also why only hash and skcipher are supported as they > > are the main algorithm types supported by teh current async > > drivers in the kernel. > > Are there any chances AEAD will be supported? Is the API extendable to > allow that? > > If I remember correctly, the original patch was simply a port of FreeBSD > /dev/crypto, which doesn't support AEAD. If it's meant to work like the FreeBSD /dev/crypto, then maybe this[1] paper is worth mentionning, which includes some performance numbers. There was a single thing that drew my attention, from "Drawbacks and problems [of userspace crypto]": "Lots of scary code-duplication". [1] http://www.paeps.cx/pubs/crypto_acceleration/slides.pdf -- Mihai Donțu -- 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