[Bug 27783] Incompatible specification for how usages is enforced for ECDH

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27783

Eric Roman <ericroman@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ericroman@google.com

--- Comment #2 from Eric Roman <ericroman@google.com> ---
I agree with Jim, the language in step 4 seems reversed.
It would make more sense if it read:

If the "d" field is *NOT* present and if usages is not empty then throw a
SyntaxError.

Which phrased differently is "public ECDH keys must have empty usages".

(The prohibition of private ECDH keys having empty usages is already covered by
the generic language of importKey() which place such a restriction on
secret/private keys)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 8 January 2015 00:33:46 UTC