From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update)
Date: Wed, 06 Apr 2016 13:05:49 -0400 [thread overview]
Message-ID: <1459962349.3166.25.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <4392.1459959890@warthog.procyon.org.uk>
On Wed, 2016-04-06 at 17:24 +0100, David Howells wrote:
> Looking in digsig.c, I see:
>
> #ifdef CONFIG_INTEGRITY_TRUSTED_KEYRING
> static bool init_keyring __initdata = true;
> #else
> static bool init_keyring __initdata;
> #endif
>
> Since this doesn't ever appear to be altered, should integrity_init_keyring()
> just be made conditionally compiled?
I'm not sure what you're asking. If you're asking if the whole file can
be include based on whether this option is enabled, then no.
Mimi
next prev parent reply other threads:[~2016-04-06 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 3:00 [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update) Mimi Zohar
2016-04-06 16:24 ` David Howells
2016-04-06 17:05 ` Mimi Zohar [this message]
2016-04-06 18:10 ` David Howells
2016-04-06 18:50 ` Mimi Zohar
2016-04-07 9:01 ` David Howells
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=1459962349.3166.25.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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