[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2100092.9meQszc5SR@tauon.chronox.de>
Date: Mon, 24 Apr 2017 08:21:46 +0200
From: Stephan Müller <smueller@...onox.de>
To: Stephan Müller <smueller@...onox.de>
Cc: Gilad Ben-Yossef <gilad@...yossef.com>,
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 Montag, 24. April 2017, 08:16:50 CEST schrieb Stephan Müller:
Hi Gilad,
> >
> > int __des3_ede_setkey(u32 *expkey, u32 *flags, const u8 *key,
> >
> > unsigned int keylen)
> >
> > However, this does not check that k1 == k3. In this case DES3
> > becomes 2DES (2-keys TDEA), the use of which was dropped post 2015
> > by NIST Special Publication 800-131A*.
>
> It is correct that the RFC wants at least a 2key 3DES. And it is correct
> that SP800-131A mandates 3key 3DES post 2015. All I am saying is that FIPS
> 140-2 does *not* require a technical verification of the 3 keys being not
> identical.
One side note: we had discussed a patch to this function in the past, see [1].
[1] https://patchwork.kernel.org/patch/8293441/
Ciao
Stephan
Powered by blists - more mailing lists