From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: dmitry.kasatkin@intel.com, linux-kernel@vger.kernel.org,
keyrings@linux-nfs.org, linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/3] KEYS: Load *.x509 files into kernel keyring
Date: Thu, 17 Jan 2013 13:44:23 -0500 [thread overview]
Message-ID: <1358448263.2689.75.camel@falcor1> (raw)
In-Reply-To: <20130117180352.27885.79893.stgit@warthog.procyon.org.uk>
On Thu, 2013-01-17 at 18:03 +0000, David Howells wrote:
> Load all the files matching the pattern "*.x509" that are to be found in kernel
> base source dir and base build dir into the module signing keyring.
Do we really want certificates cluttering up the base source tree? Any
reason not to define an x509 directory?
> The "extra_certificates" file is then redundant.
Ok.
Mimi
prev parent reply other threads:[~2013-01-17 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 18:03 [PATCH 1/3] KEYS: Load *.x509 files into kernel keyring David Howells
2013-01-17 18:04 ` [PATCH 2/3] KEYS: Separate the kernel signature checking keyring from module signing David Howells
2013-01-17 18:57 ` Mimi Zohar
2013-01-17 21:20 ` David Howells
2013-01-17 18:04 ` [PATCH 3/3] KEYS: Add a 'trusted' flag and a 'trusted only' flag David Howells
2013-01-30 8:29 ` Kasatkin, Dmitry
2013-01-30 10:32 ` David Howells
2013-02-06 22:18 ` Kasatkin, Dmitry
2013-01-17 18:44 ` Mimi Zohar [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=1358448263.2689.75.camel@falcor1 \
--to=zohar@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-crypto@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