linux-kernel - Re: [PATCH 00/22] KEYS: Support TPM-wrapped key and crypto ops

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20622.1537291117@warthog.procyon.org.uk>
Date:   Tue, 18 Sep 2018 18:18:37 +0100
From:   David Howells <dhowells@...hat.com>
To:     Denis Kenzior <denkenz@...il.com>
Cc:     dhowells@...hat.com, David Woodhouse <dwmw2@...radead.org>,
        jmorris@...ei.org, keyrings@...r.kernel.org,
        linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/22] KEYS: Support TPM-wrapped key and crypto ops

Denis Kenzior <denkenz@...il.com> wrote:

> > Yes.  It shouldn't be much code, either.  You still have to check for X.509
> > DER since the kernel currently supports that.
> 
> For reasons of backward compatibility, correct?  The kernel also has
> mscode.asn1 which we would need to support as well.  Since we can't break
> compatibility then perhaps this doesn't buy us a whole lot in the end.

Don't worry about mscode - that's not an asymmetric key parser.  That's only
ever used directly from verify_pefile_signature().

Currently, we have to retain support for DER-encoded X.509.

But there's no reason we can't have a PEM parser that decodes the PEM and
selects X.509, PKCS#8 or TPM based on the ascii header in that.  PKCS#8 and
TPM don't need to take DER directly.

David