From: Petko Manolov <petkan@mip-labs.com>
To: David Howells <dhowells@redhat.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
dwmw2@infradead.org, David Woodhouse <David.Woodhouse@intel.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [RFC PATCH] X.509: Don't check the signature on apparently self-signed keys [ver #2]
Date: Wed, 6 Jan 2016 19:00:08 +0200 [thread overview]
Message-ID: <20160106170008.GF4603@localhost> (raw)
In-Reply-To: <9026.1452086487@warthog.procyon.org.uk>
On 16-01-06 13:21:27, David Howells wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> > The x509_validate_trust() was originally added for IMA to ensure, on a
> > secure boot system, a certificate chain of trust rooted in hardware. The IMA
> > MOK keyring extends this certificate chain of trust to the running system.
>
> The problem is that because 'trusted' is a boolean, a key in the IMA MOK
> keyring will permit addition to the system keyring.
If this is true the i am clearly doing the wrong thing. The CA hierarchy should
run top-bottom, not the other way around.
IMA MOK was introduced mainly because .system keyring was static at the time.
Assuming i have my root certificate in .system how can i add more keys to this
keyring? The new keys have been signed by my root CA? Is this possible since
your October patch-set or i've been missing something this whole time?
Petko
next prev parent reply other threads:[~2016-01-06 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 15:47 [RFC PATCH] X.509: Don't check the signature on apparently self-signed keys [ver #2] David Howells
2016-01-05 15:55 ` David Howells
2016-01-05 16:08 ` Mimi Zohar
2016-01-05 16:39 ` David Howells
2016-01-06 12:22 ` Mimi Zohar
2016-01-06 13:21 ` David Howells
2016-01-06 14:03 ` Mimi Zohar
2016-01-06 14:19 ` David Howells
2016-01-06 17:00 ` Petko Manolov [this message]
2016-01-05 16:40 ` David Howells
2016-01-05 17:00 ` Petko Manolov
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=20160106170008.GF4603@localhost \
--to=petkan@mip-labs.com \
--cc=David.Woodhouse@intel.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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.