From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 Howells <dhowells@redhat.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: Re: [PULL] modules
Date: Sun, 14 Oct 2012 22:27:54 +0100 [thread overview]
Message-ID: <20121014222754.0f11b609@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CA+55aFyVcTT4tKTVvhzXz3t4uw=MDLU00NAAOacWt6i3xovERg@mail.gmail.com>
> I realize that fips_enabled is only for crazy people, but it's exactly
> code like this that limits it to only crazy people. Is there some
> *reason* for this?
Presumably its so a typical server with reboot on panic will reboot so
the attacker can hide the attempt better ;-)
Alan
next prev parent reply other threads:[~2012-10-14 21:23 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 [this message]
2012-10-15 7:50 ` FIPS-mode panic? (was Re: [PULL] modules) David Howells
2012-10-15 11:28 ` 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=20121014222754.0f11b609@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--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=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