From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stephan Mueller <sm@eperm.de>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
herbert@gondor.apana.org.au, davem@davemloft.net,
linux-doc@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: Add a flag allowing the self-tests to be disabled at runtime.
Date: Fri, 29 Apr 2016 12:04:46 +0100 [thread overview]
Message-ID: <20160429110446.GD28599@redhat.com> (raw)
In-Reply-To: <1716181.h8M5zx62aT@tauon.atsec.com>
On Fri, Apr 29, 2016 at 12:59:57PM +0200, Stephan Mueller wrote:
> Am Freitag, 29. April 2016, 11:07:43 schrieb Richard W.M. Jones:
>
> Hi Richard,
[...]
> > + if (notests) {
>
> What about if (!fips_enabled && notests) ?
>
> I am not sure whether the kernel should prevent mistakes in user space. A
> mistake would be when setting fips=1 and notests=1 as the FIPS mode mandates
> the self tests.
(Sorry, I just posted v2 before I saw this message.) I saw the FIPS
stuff and thought about that. Should we prevent mistakes like that?
I really don't know.
Rich.
> > + pr_info("alg: self-tests disabled\n");
> > + return 0;
> > + }
> > +
> > alg_test_descs_check_order();
> >
> > if ((type & CRYPTO_ALG_TYPE_MASK) == CRYPTO_ALG_TYPE_CIPHER) {
>
>
> Ciao
> Stephan
> --
> | Nimm das Recht weg - |
> | was ist dann der Staat noch anderes als eine große Räuberbande? |
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
prev parent reply other threads:[~2016-04-29 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 10:07 [PATCH] crypto: Add a flag allowing the self-tests to be disabled at runtime Richard W.M. Jones
2016-04-29 10:07 ` Richard W.M. Jones
2016-04-29 10:59 ` Stephan Mueller
2016-04-29 11:04 ` Richard W.M. Jones [this message]
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=20160429110446.GD28599@redhat.com \
--to=rjones@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sm@eperm.de \
/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