Re: ASN.1 encoding. What is wrong and some possible ways forward. from Ryan Sleevi on 2016-03-29 (public-webcrypto@w3.org from March 2016)

From: Ryan Sleevi <sleevi@google.com>
Date: Tue, 29 Mar 2016 11:00:52 -0700
To: Jason Proctor <jason@mono.hm>
Cc: Axel Nennker <Axel.Nennker@telekom.de>, Ryan Hurst <rmh@google.com>, Jim Schaad <ietf@augustcellars.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Tim Taubert <ttaubert@mozilla.com>
Message-ID: <CACvaWvbEbFMSWXmWP1b7GMG3UV9dtKv2V2HzPOT6nD8-0CsTQg@mail.gmail.com>

On Tue, Mar 29, 2016 at 8:33 AM, Jason Proctor <jason@mono.hm> wrote:

> i for one have to redo my entire web client strategy if we lose it.
>

Can you explain why this is? Why doesn't simply using asn1.js to ingest the
BER/DER data and spit out a JWK for import, or, on export, take a JWK and
convert using asn1.js to BER/DER, suffice?

What functionality is provided by the ASN.1 support that cannot simply be
done by converting to/from JWK?

Received on Tuesday, 29 March 2016 18:02:00 UTC