I concur with Hubert, and think that DER in this context is perfectly OK. On 10/2/19, 6:59 AM, "TLS on behalf of Hubert Kario" <tls-boun...@ietf.org on behalf of hka...@redhat.com> wrote:
On Wednesday, 2 October 2019 00:15:13 CEST Peter Gutmann wrote:
> Hubert Kario <hka...@redhat.com> writes:
> >a lax DER parser sounds like an oxymoron to me... :)
>
> That's why I assumed it was an accident/error. Writing a spec that relies
> on buggy parser implementations in order to work is asking for trouble.
well, SEC 1 does not require the ECDSA-Sig-Value structure to be encoded
with
DER, it's TLS that does that (and I'd say for the better, given the
multitude
of ways you can encode SEQUENCE in BER...)
--
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
