[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15593683.jmSB8WjLMD@tachyon.chronox.de>
Date: Tue, 16 Jun 2015 04:19:52 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Tadeusz Struk <tadeusz.struk@...el.com>
Cc: herbert@...dor.apana.org.au, linux-kernel@...r.kernel.org,
keescook@...omium.org, jwboyer@...hat.com, richard@....at,
steved@...hat.com, qat-linux@...el.com, dhowells@...hat.com,
linux-crypto@...r.kernel.org, james.l.morris@...cle.com,
jkosina@...e.cz, zohar@...ux.vnet.ibm.com, davem@...emloft.net,
vgoyal@...hat.com
Subject: Re: [PATCH RFC v5 3/4] crypto: rsa: add a new rsa generic implementation
Am Montag, 15. Juni 2015, 18:49:15 schrieb Tadeusz Struk:
Hi Tadeusz,
> On 06/15/2015 04:23 PM, Stephan Mueller wrote:
> >> + /* In FIPS mode only allow key size minimum 2K */
> >>
> >> > + if (fips_enabled && (mpi_get_size(key->n) < 256)) {
> >
> > Considering my previous email, shouldn't that check rather be
> >
> > if (fips_enabled &&
> >
> > ((mpi_get_size(key->n) != 256) || (mpi_get_size(key->n) != 384))
>
> I'm not familiar with the FIPS requirements. I checked the NIST
> recommendations witch states that RSA: |n| >= 2048 is acceptable. If FIPS
> allows 2K and 3K only then we need to change it.
The reason for exclusive 2k/3k is the CAVS testing: there is only the ability
to test 2/3k. Longer key sizes are even not allowed as per SP800-131A in favor
of EC.
--
Ciao
Stephan
--
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