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: <ab3f4f96-6aec-4586-21fa-318fcee997a5@linux.ibm.com>
Date:   Mon, 1 Feb 2021 11:45:16 -0500
From:   Stefan Berger <stefanb@...ux.ibm.com>
To:     David Howells <dhowells@...hat.com>
Cc:     keyrings@...r.kernel.org, linux-crypto@...r.kernel.org,
        davem@...emloft.net, herbert@...dor.apana.org.au,
        zohar@...ux.ibm.com, linux-kernel@...r.kernel.org,
        patrick@...terwijk.org, linux-integrity@...r.kernel.org
Subject: Re: [PATCH v7 0/4] Add support for x509 certs with NIST p256 and p192
 keys

On 2/1/21 11:36 AM, David Howells wrote:
> Stefan Berger <stefanb@...ux.ibm.com> wrote:
>
>> 1) the whole series goes through the crypto tree
>>
>> 2) I make the OIDs addition patch 1 that both keyrings and crypto take
>> separately?
> The first might be easiest, but 2 is okay also.  You'll just need to give
> myself and Herbert separate branches to pull, rooted on the same commit.
>
> Btw, what do patches 2-4 do if patch 1 isn't applied?

With the crypto module missing in the kernel you will get an error 
trying to load an x509 certificate that needs the algorithm to verify 
the self-signed signature.

Before I post yet another series I hope that Herbert can say whether 
option 1) would work for him.

    Stefan


>
>
> David
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ