From: Kyle McMartin <kmcmarti@redhat.com>
To: Stephan Mueller <stephan.mueller@atsec.com>
Cc: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
jstancek@redhat.com
Subject: Re: [PATCH] MODSIGN: only panic in fips mode if sig_enforce is set
Date: Thu, 24 Jan 2013 09:59:07 -0500 [thread overview]
Message-ID: <20130124145907.GG6538@redacted.bos.redhat.com> (raw)
In-Reply-To: <50FFFF48.6020608@atsec.com>
On Wed, Jan 23, 2013 at 04:18:32PM +0100, Stephan Mueller wrote:
> 3. in the cipher initialization code of the crypto API (i.e. the one
> behind crypto_register_alg()), you check the signature check flag --
> panic the kernel when the flag shows that the signature check failed
>
> This way you limit the panic on signature checks in FIPS mode to the
> crypto modules.
>
I was hoping we could just do what we do for driver/staging and set a
flag in modpost for crypto modules, but it looks like since we have
crypto modules outside of crypto/ for things like aesni, that won't
work. Maybe that is a better choice, but it seems like an awful kludge.
--Kyle
next prev parent reply other threads:[~2013-01-24 14:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 18:43 [PATCH] MODSIGN: only panic in fips mode if sig_enforce is set Kyle McMartin
2013-01-22 23:17 ` Rusty Russell
2013-01-23 11:26 ` David Howells
2013-01-23 15:18 ` Stephan Mueller
2013-01-24 14:59 ` Kyle McMartin [this message]
2013-01-25 11:28 ` Stephan Mueller
2013-01-24 19:06 ` [PATCH] MODSIGN: flag modules that use cryptoapi and only panic if those are unsigned Kyle McMartin
2013-01-24 19:21 ` Kyle McMartin
2013-01-24 23:36 ` Rusty Russell
2013-01-25 5:45 ` Kyle McMartin
2013-01-25 12:42 ` Stephan Mueller
2013-02-03 23:34 ` Rusty Russell
2013-01-25 12:46 ` Stephan Mueller
2013-01-25 12:18 ` Stephan Mueller
2013-02-05 22:58 ` [RFC PATCH] fips: check whether a module registering an alg or template is signed Kyle McMartin
2013-02-06 8:02 ` Stephan Mueller
2013-02-06 16:15 ` Kyle McMartin
2013-02-06 17:45 ` Stephan Mueller
2013-02-06 18:18 ` Kyle McMartin
2013-01-25 0:14 ` [PATCH] MODSIGN: flag modules that use cryptoapi and only panic if those are unsigned David Howells
2013-01-25 3:20 ` Matthew Garrett
2013-01-25 12:23 ` Stephan Mueller
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=20130124145907.GG6538@redacted.bos.redhat.com \
--to=kmcmarti@redhat.com \
--cc=dhowells@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stephan.mueller@atsec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.