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, 28 May 2019 08:20:29 +0000 From: Horia Geanta <horia.geanta@....com> To: Christophe Leroy <christophe.leroy@....fr>, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net> CC: "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org> Subject: Re: [PATCH v1 08/15] crypto: talitos - Do not modify req->cryptlen on decryption. On 5/21/2019 4:34 PM, Christophe Leroy wrote: > For decrypt, req->cryptlen includes the size of the authentication > part while all functions of the driver expect cryptlen to be > the size of the encrypted data. > > As it is not expected to change req->cryptlen, this patch > implements local calculation of cryptlen. > An alternative would be to restore req->cryptlen in the *_done() callback. It would be easier to implement, though probably less intuitive. Horia
Powered by blists - more mailing lists