linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	aquini@redhat.com, jeremy.wayne.powell@gmail.com,
	clemens@ladisch.de, pwalten@au1.ibm.com, joe@perches.com
Subject: Re: [PATCH v7 0/6] SP800-90A Deterministic Random Bit Generator
Date: Fri, 30 May 2014 12:08:08 +0200	[thread overview]
Message-ID: <1743692.XvreuYbNlX@myon.chronox.de> (raw)
In-Reply-To: <20140530090548.GA12603@gondor.apana.org.au>

Am Freitag, 30. Mai 2014, 17:05:48 schrieb Herbert Xu:

Hi Herbert,

> On Mon, May 26, 2014 at 07:42:57AM +0200, Stephan Mueller wrote:
> > A second aspect is the implementation of the stdrng. Currently, the
> > offered
> > patch does not include the stdrng selection. I am currently working on the
> > completion of the addition of the stdrng selection to the offered patch.
> > My
> > idea is the following: currently, all DRBG types are registered with their
> > own cra_name. However, there shall be one particular DRBG registered
> > twice. When registering the instance again, the cra_name shall be
> > "stdrng". In addition, if the kernel command line contains fips=1, the
> > cra_priority of that stdrng should be set to 300. That implies that when
> > the kernel resolves the stdrng, it resolves to get_random_bytes in normal
> > mode, but to the stdrng DRBG in FIPS mode.
> 
> Just have all of them register as stdrng with differing priorities.

Will do. Just to clarify: I would use priorities below 200 if (!fips_enabled) 
and above 200 for fips_enabled. This would mean that per default, the 
get_random_bytes/krng has the highest priority in non-fips mode. In FIPS mode, 
the DRBGs would have the higher priority per default.

> We already have a user-space interface to change priorities.

Great -- if I may ask, which interface is that?
> 
> Cheers,


Ciao
Stephan
-- 
| Cui bono? |

  reply	other threads:[~2014-05-30 10:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21  4:18 [PATCH v7 0/6] SP800-90A Deterministic Random Bit Generator Stephan Mueller
2014-05-21  4:18 ` [PATCH v7 1/6] " Stephan Mueller
2014-05-21 20:17   ` Stephan Mueller
2014-05-23 21:10   ` Herbert Xu
2014-05-26  5:44     ` Stephan Mueller
2014-05-21  4:19 ` [PATCH v7 2/6] header file for DRBG Stephan Mueller
2014-05-21  4:20 ` [PATCH v7 3/6] DRBG kernel configuration options Stephan Mueller
2014-05-21  4:21 ` [PATCH v7 4/6] compile the DRBG code Stephan Mueller
2014-05-21  4:21 ` [PATCH v7 5/6] DRBG testmgr test vectors Stephan Mueller
2014-05-21  4:22 ` [PATCH v7 6/6] Add DRBG test code to testmgr Stephan Mueller
2014-05-23 21:14 ` [PATCH v7 0/6] SP800-90A Deterministic Random Bit Generator Herbert Xu
2014-05-26  5:42   ` Stephan Mueller
2014-05-30  9:05     ` Herbert Xu
2014-05-30 10:08       ` Stephan Mueller [this message]
2014-05-30 10:52         ` Herbert Xu

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=1743692.XvreuYbNlX@myon.chronox.de \
    --to=smueller@chronox.de \
    --cc=aquini@redhat.com \
    --cc=clemens@ladisch.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jeremy.wayne.powell@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwalten@au1.ibm.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 NNTP newsgroup(s).