- From: Eric Roman <ericroman@google.com>
- Date: Mon, 1 Aug 2016 16:13:40 -0700
- To: Harry Halpin <hhalpin@w3.org>
- Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Received on Monday, 1 August 2016 23:14:14 UTC
On Mon, Aug 1, 2016 at 1:46 PM, Harry Halpin <hhalpin@w3.org> wrote: > Summary: > > - Since spki/pkcs keys work so far in test-suite, only make > non-normative in places where there is an explicit lack of interop in > test-suite and add informative text warning re possible key format > incompatibilities in some cases. > Do we have data (or an intuition) of what the most painful implementation incompatibilities are for real-world consumers of Web Crypto? On the Chrome side, the main issue I am aware of is that Chrome cannot import ECDH keys exported by Firefox ( https://bugs.chromium.org/p/chromium/issues/detail?id=532728), due to not supporting id-ecDH (1.3.132.1.12). I would like to address this. Certainly that isn't the only incompatibility, but does seem to be one that matters to developers. Is there any other feedback from Web Crypto consumers on how viable SPKI/PKCS8 has been in implementations, and if not what the biggest roadblocks are? > - Next meeting August 22nd, need to close all issues. > > Available here: > > https://www.w3.org/2016/08/01-crypto-minutes.html > > >
Received on Monday, 1 August 2016 23:14:14 UTC