linux-kernel - Re: [RFC PATCH 0/7] KEYS: Adjust public key signature handling

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1456920627.2780.60.camel@linux.vnet.ibm.com>
Date:	Wed, 02 Mar 2016 07:10:27 -0500
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	keyrings@...r.kernel.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/7] KEYS: Adjust public key signature handling

Hi David,

On Mon, 2016-02-29 at 18:21 +0000, David Howells wrote:
> These patches do the following:
> 
>  (1) Retain a signature in an asymmetric-type key and associate with it the
>      identifiers that will match a key that can be used to verify it.
> 
>  (2) Differentiate an X.509 cert that cannot be used versus one that cannot
>      be verified due to unavailable crypto.  This is noted in the
>      structures involved.
> 
>  (3) Determination of the self-signedness of an X.509 cert is improved to
>      include checks on the subject/issuer names and the key
>      algorithm/signature algorithm types.
> 
>  (4) Self-signed X.509 certificates are consistency checked early on if the
>      appropriate crypto is available.
> 
> This set of patches is a prelude to a set that changes how trustworthiness
> is determined.

These patches don't apply directly on top of linux-security.   Maybe
they apply on top of an updated version of the  "X.509: Software public
key subtype changes" patch set.   In which branch are these patches?

thanks,

Mimi