Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1338155

Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2]

From Mimi Zohar <zohar@linux.vnet.ibm.com>
Newsgroups linux.kernel
Subject Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2]
Date 2016-02-19 13:20 +0100
Message-ID <r3Scq-4Z3-13@gated-at.bofh.it> (permalink)
References <r0IsV-6rW-3@gated-at.bofh.it> <qSCNI-78i-3@gated-at.bofh.it> <qSCNI-78i-7@gated-at.bofh.it> <r3RT5-4A8-37@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, 2016-02-19 at 11:58 +0000, David Howells wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> 
> > As discussed, "restrict_link_by_system_trusted" is not enough.  The
> > certificate being added should be in a revoked list as well.
> 
> What do you mean be a "revoked list"?  There currently isn't such a beast in
> IMA.  The patches I've proposed should make the functionality available
> approximately the same as exists now.

Support for the IMA mok and blacklist keyrings are disabled by default.
Please don't make this the default, at least until we add the equivalent
of revoked certificates.  Refer to the "Re: How to add additional
blacklist entries?"  thread.

Mimi

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2] Mimi Zohar <zohar@linux.vnet.ibm.com> - 2016-02-10 20:20 +0100
  Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2] David Howells <dhowells@redhat.com> - 2016-02-19 13:00 +0100
    Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2] Mimi Zohar <zohar@linux.vnet.ibm.com> - 2016-02-19 13:20 +0100

csiph-web