From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755348AbdDQViw (ORCPT ); Mon, 17 Apr 2017 17:38:52 -0400 Received: from namei.org ([65.99.196.166]:41844 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754749AbdDQViu (ORCPT ); Mon, 17 Apr 2017 17:38:50 -0400 Date: Tue, 18 Apr 2017 07:38:45 +1000 (AEST) From: James Morris To: David Howells 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 In-Reply-To: <18309.1492008274@warthog.procyon.org.uk> Message-ID: References: <18309.1492008274@warthog.procyon.org.uk> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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