[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3d8a1ce-a982-2662-28f6-3c06cb679d5f@linux.vnet.ibm.com>
Date: Thu, 16 Sep 2021 16:05:01 -0400
From: Nayna <nayna@...ux.vnet.ibm.com>
To: Eric Snowberg <eric.snowberg@...cle.com>, keyrings@...r.kernel.org,
linux-integrity@...r.kernel.org, zohar@...ux.ibm.com,
dhowells@...hat.com, dwmw2@...radead.org,
herbert@...dor.apana.org.au, davem@...emloft.net,
jarkko@...nel.org, jmorris@...ei.org, serge@...lyn.com
Cc: keescook@...omium.org, gregkh@...uxfoundation.org,
torvalds@...ux-foundation.org, scott.branden@...adcom.com,
weiyongjun1@...wei.com, nayna@...ux.ibm.com, ebiggers@...gle.com,
ardb@...nel.org, nramas@...ux.microsoft.com, lszubowi@...hat.com,
linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
linux-security-module@...r.kernel.org,
James.Bottomley@...senPartnership.com, pjones@...hat.com,
konrad.wilk@...cle.com
Subject: Re: [PATCH v6 03/13] KEYS: CA link restriction
On 9/14/21 5:14 PM, Eric Snowberg wrote:
> Add a new link restriction. Restrict the addition of keys in a keyring
> based on the key to be added being a CA (self-signed).
A self-signed cert can be a root CA cert or a code-signing cert. The way
to differentiate a CA cert is by checking BasicConstraints CA:TRUE and
keyUsage:keyCertSign. Refer to Section Basic Constraints and Key Usage
in the document - https://datatracker.ietf.org/doc/html/rfc5280.
Thanks & Regards,
- Nayna
Powered by blists - more mailing lists