On Fri, 2015-05-22 at 08:48 +0100, David Howells wrote: > Luis R. Rodriguez <mcg...@suse.com> wrote: > > > > This is similar to what i am doing right now - create CA hierarchy so we > > > can > > > have something like: > > > > > > +-> KeyB > > > | > > > RootCA ---> CertA ---> CertB ---> CertC ---> KeyC > > > | > > > +-> CertA' ---> KeyA" > > > > How exactly do you go about uploading CertB to the kernel BTW? > > Assuming RootCA or CertA is present in the kernel, the idea would be to use > the add_key() system call or the request_key() mechanism to add the key to the > system keyring. The key in the cert would only be added to the keyring if it > is trusted by a key already there.
>From Petko's description, the RootCA is on the system keyring, but CertA is on a new IMA trusted CA keyring. So everything you said is true, but on this new, yet to be upstreamed, IMA trusted CA keyring. Mimi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
