Re: Open implementation bugs that effect spec

On Wed, Jan 20, 2016 at 7:01 PM, Harry Halpin <hhalpin@w3.org> wrote:

>
> b) JWK:
> JWK "use" fields not parsed:
> Edge: https://connect.microsoft.com/IE/Feedback/Details/2242108
> Chrome: https://code.google.com/p/chromium/issues/detail?id=441995
> Chrome: Optional JWK fields not typed checked:
> https://code.google.com/p/chromium/issues/detail?id=385376
> Chrome: Spec Bug: References to JOSE JWA/JWK need to be updated:
> https://code.google.com/p/chromium/issues/detail?id=571114
> JWK serializer should use unpadded websafe base64 (seems fixed?)
> https://code.google.com/p/chromium/issues/detail?id=364749
> Spec compliance: Should reject JWK if "oth" is specified (i.e. get rid of
> multi-primes)
> https://code.google.com/p/chromium/issues/detail?id=441396
>
>
I'm not aware of open bugs, but AIUI, Firefox accepts non-minimal
BigInteger encodings in JWK (
https://code.google.com/p/chromium/issues/detail?id=383998)

If you're going through issues, you should also look for those with the
WebCrypto tag that have been WontFix'd.