linux-kernel - Re: [PATCH v1 0/9] Enable root to update the blacklist keyring

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]

Date:   Fri, 4 Dec 2020 17:38:27 +0200
From:   Jarkko Sakkinen <jarkko@...nel.org>
To:     David Howells <dhowells@...hat.com>
Cc:     =?UTF-8?Q?Micka=c3=abl_Sala=c3=bcn?= 
        <mic@...ikod.net>, David Woodhouse <dwmw2@...radead.org>,
        "David S . Miller" <davem@...emloft.net>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        James Morris <jmorris@...ei.org>,
        =?UTF-8?Q?Micka=c3=abl_Sala=c3=bcn?= 
        <mic@...ux.microsoft.com>, Mimi Zohar <zohar@...ux.ibm.com>,
        "Serge E . Hallyn" <serge@...lyn.com>, keyrings@...r.kernel.org,
        linux-crypto@...r.kernel.org, linux-integrity@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH v1 0/9] Enable root to update the blacklist keyring

On Fri, Dec 04, 2020 at 02:01:36PM +0000, David Howells wrote:
> Mickaël Salaün <mic@...ikod.net> wrote:
> 
> > > What would be easiest way to smoke test the changes?
> > 
> > An easy way to test it is to enable the second trusted keyring to
> > dynamically load certificates in the kernel. Then we can create a hash
> > of a valid certificate (but not loaded yet) and sign it as explained in
> > tools/certs/print-cert-tbs-hash.sh (patch 9/9). Once this hash is loaded
> > in the kernel, loading the blacklisted certificate will be denied. We
> > can also test it with a PKCS#7 signature chain, either with the
> > blacklist keyring itself, or with a signed dm-verity image.
> 
> It might also be possible to use the pkcs#7 test key type
> (CONFIG_PKCS7_TEST_KEY) to aid in that.
> 
> David

Thanks, note taken.

/Jarkko