[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19392241.HaQDpS1BQU@positron.chronox.de>
Date: Sun, 23 Apr 2017 20:57:58 +0200
From: Stephan Müller <smueller@...onox.de>
To: Gilad Ben-Yossef <gilad@...yossef.com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, linux-crypto@...r.kernel.org,
devicetree@...r.kernel.org,
Linux kernel mailing list <linux-kernel@...r.kernel.org>,
Gilad Ben-Yossef <gilad.benyossef@....com>,
Binoy Jayan <binoy.jayan@...aro.org>,
Ofir Drang <ofir.drang@....com>,
Stuart Yoder <stuart.yoder@....com>
Subject: Re: [PATCH v2 6/9] staging: ccree: add FIPS support
Am Sonntag, 23. April 2017, 11:48:58 CEST schrieb Gilad Ben-Yossef:
Hi Gilad,
> I do wonder if there is value in alternate behavior of stopping crypto
> API on FIPS error rather than a panic though. I will try to get an
> explanation why we do it this way.
In FIPS, all crypto function must cease if a self test fails. This can be done
by instrumenting the crypto API calls with a check to a global flag or by
simply terminating the entire "FIPS module".
The panic() is the simplest approach to meet that requirement.
Ciao
Stephan
Powered by blists - more mailing lists