LKML Archive mirror
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Hui Tang <tanghui20@huawei.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
	xuzaibo@huawei.com, wangzhou1@hisilicon.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] crypto: ecdh - fix 'ecdh_init'
Date: Fri, 21 May 2021 11:36:37 +0200	[thread overview]
Message-ID: <878011e1735e84d4e16ab68d9f03e2f62b531314.camel@chronox.de> (raw)
In-Reply-To: <20210521081356.3bnytzdxhjkgzb7g@gondor.apana.org.au>

Am Freitag, dem 21.05.2021 um 16:13 +0800 schrieb Herbert Xu:
> On Fri, May 21, 2021 at 04:08:10PM +0800, Hui Tang wrote:
> 
> 
> Stephan, can you confirm that both ecdh-nist-p192 and ecdsa-nist-p192
> should be disabled in FIPS mode?

Confirmed with the following caveat: sigver is allowed due to legacy
considerations. Siggen / ECDH is only allowed for curves P-224 and higher.

As we introduce ECDSA today, I would not consider a legacy mode and thus
disable P-192.

Ciao
Stephan



  reply	other threads:[~2021-05-21  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  6:39 [PATCH 0/3] crypto: ecdh - register NIST P384 Hui Tang
2021-05-12  6:40 ` [PATCH 1/3] crypto: ecdh - fix 'ecdh_init' Hui Tang
2021-05-21  7:45   ` Herbert Xu
2021-05-21  8:08     ` Hui Tang
2021-05-21  8:13       ` Herbert Xu
2021-05-21  9:36         ` Stephan Mueller [this message]
2021-05-12  6:40 ` [PATCH 2/3] crypto: ecdh - register NIST P384 tfm Hui Tang
2021-05-12  6:40 ` [PATCH 3/3] crypto: ecdh - add test suite for NIST P384 Hui Tang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878011e1735e84d4e16ab68d9f03e2f62b531314.camel@chronox.de \
    --to=smueller@chronox.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tanghui20@huawei.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=xuzaibo@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).