linux-kernel - Re: [GIT PULL] KEYS: Blacklisting, restrictions and DH

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.20.1704180738310.11039@namei.org>
Date:   Tue, 18 Apr 2017 07:38:45 +1000 (AEST)
From:   James Morris <jmorris@...ei.org>
To:     David Howells <dhowells@...hat.com>
cc:     keyrings@...r.kernel.org, linux-security-module@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KEYS: Blacklisting, restrictions and DH

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@...ei.org>