[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21602.1547655320@warthog.procyon.org.uk>
Date: Wed, 16 Jan 2019 16:15:20 +0000
From: David Howells <dhowells@...hat.com>
To: Vitaly Chikunov <vt@...linux.org>
Cc: dhowells@...hat.com, Stephan Mueller <smueller@...onox.de>,
Herbert Xu <herbert@...dor.apana.org.au>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 4/4] crypto: Add EC-RDSA algorithm
Vitaly Chikunov <vt@...linux.org> wrote:
> > Regarding your comment (2), I am not sure I understand. Why do you say that
> > the DER format cannot be parsed by the kernel's ASN.1 parser? For example,
>
> It can, but DER is stricter than BER. For example, in DER 'OCTET STRING'
> length field should be encoded in just one byte if it's smaller than
> 128, in BER it could be encoded in multiple encodings. This does not
> seem like a big deal, though. With BER decoder an improperly DER-encoded
> certificate could be successfully parsed.
Whilst that is true, I don't think it's that big a deal. DER is a subset of
BER, so a BER decoder ought to be able to parse it. Note that X.509 is
supposed to be DER, but we use a BER decoder for that too.
David
Powered by blists - more mailing lists