From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KEYS: Blacklisting, restrictions and DH
Date: Tue, 18 Apr 2017 07:38:45 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704180738310.11039@namei.org> (raw)
In-Reply-To: <18309.1492008274@warthog.procyon.org.uk>
On Wed, 12 Apr 2017, David Howells wrote:
>
> Hi James,
>
> Could you pull these changes into security/next please:
>
> (1) Provide a blacklist keyring and a blacklist key type such that X.509
> keys and PKCS#7 certs can be blacklisted. It is possible to load the
> blacklist from a file at compile time. A future patch will
> additionally load the blacklist from the UEFI blacklist if available.
>
> (2) Make it possible to create a userspace keyring and to apply a
> restriction to it such that no new keys can be added unless they meet
> the criteria.
>
> (3) Add SP800-56A KDF support for the DH operation.
>
Pulled, thanks.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2017-04-17 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 14:44 [GIT PULL] KEYS: Blacklisting, restrictions and DH David Howells
2017-04-17 21:38 ` James Morris [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=alpine.LRH.2.20.1704180738310.11039@namei.org \
--to=jmorris@namei.org \
--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;
as well as URLs for NNTP newsgroup(s).