From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Stephan Mueller <stephan.mueller@atsec.com>
Cc: dhowells@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
LKML <linux-kernel@vger.kernel.org>,
Alex Lyashkov <umka@cloudlinux.com>,
Arnd Bergmann <arnd@arndb.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Kasatkin <dmitry.kasatkin@intel.com>,
Herbert Xu <herbert@gondor.hengli.com.au>,
Josh Boyer <jwboyer@redhat.com>,
linux-crypto@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Milan Broz <mbroz@redhat.com>, Ralf Baechle <ralf@linux-mips.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Sam Ravnborg <sam@ravnborg.org>
Subject: FIPS-mode panic? (was Re: [PULL] modules)
Date: Mon, 15 Oct 2012 08:50:54 +0100 [thread overview]
Message-ID: <15269.1350287454@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+55aFyVcTT4tKTVvhzXz3t4uw=MDLU00NAAOacWt6i3xovERg@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Hmm. So this thing makes me wonder:
>
> /* Not having a signature is only an error if we're strict. */
> if (err < 0 && fips_enabled)
> panic("Module verification failed with error %d in FIPS mode\n",
> err);
>
> do we really want to panic (even in fips_enabled mode)?
That's what the FIPS people want. As I understand it, if there's some
indication that the crypto stuff is compromised, the box should be shut down
immediately.
I've added Stephan Mueller to see if he can illuminate further.
David
next prev parent reply other threads:[~2012-10-15 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 9:57 [PULL] modules Rusty Russell
2012-10-14 20:11 ` Linus Torvalds
2012-10-14 20:53 ` Linus Torvalds
2012-10-14 21:27 ` Alan Cox
2012-10-15 7:50 ` David Howells [this message]
2012-10-15 11:28 ` FIPS-mode panic? (was Re: [PULL] modules) Stephan Mueller
2012-10-15 9:16 ` [PULL] modules Rusty Russell
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=15269.1350287454@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=dmitry.kasatkin@intel.com \
--cc=herbert@gondor.hengli.com.au \
--cc=jwboyer@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mbroz@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=ralf@linux-mips.org \
--cc=rdunlap@xenotime.net \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=stephan.mueller@atsec.com \
--cc=torvalds@linux-foundation.org \
--cc=umka@cloudlinux.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