| 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: <201407101331.25786.marex@denx.de> Date: Thu, 10 Jul 2014 13:31:25 +0200 From: Marek Vasut <marex@...x.de> To: Dmitry Kasatkin <d.kasatkin@...sung.com> Cc: Dmitry Kasatkin <dmitry.kasatkin@...il.com>, Mimi Zohar <zohar@...ux.vnet.ibm.com>, linux-ima-devel@...ts.sourceforge.net, "linux-security-module" <linux-security-module@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-crypto" <linux-crypto@...r.kernel.org> Subject: Re: [PATCH v3 1/3] ima: use ahash API for file hash calculation On Thursday, July 10, 2014 at 01:18:41 PM, Dmitry Kasatkin wrote: [...] > > All right, that was my understanding of the entire discussion -- an > > accelerator dying mid-way and what will IMA do about that. > > > >> But as we fallback to early allocated shash, which is not USB yet, > >> then there is no problem. > >> ahash itself does not bring any other additional problem than shash > >> itself. They are compiled builtin together. > > > > Sure, I understood that. But what will happen if the ahash accelerator > > stops working mid-flight, will IMA also go bonkers or is there some > > graceful stop? > > shash fallback will be used. Ah, thank you for clearing this! Best regards, Marek Vasut -- 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