27404 2014-11-21 22:20:36 +0000 Should check the publicKey's algorithm.name for ECDH's deriveBits()? 2016-05-23 22:56:14 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Linux RESOLVED MOVED P2 normal --- 1 ericroman sleevi ietf mitar.w3 public-webcrypto virginie.galindo watsonm oldest_to_newest 115319 0 ericroman 2014-11-21 22:20:36 +0000 ECDH's deriveBits() tests that: * baseKey.algorithm.name == "ECDH" * publicKey.type == "public" * publicKey.algorithm.namedCurve == baseKey.algorithm.namedCurve However it does not test that: * publicKey.algorithm.name == baseKey.algorithm.name Not sure if this is intentional, but that would mean passing some other public EC key (say for ECDSA) is allowed by the spec. Whereas the rest of WebCrypto is fairly particular about restricting key usage cross-algorithm. 125353 1 ietf 2016-03-04 02:05:16 +0000 I agree that this check should be added 126484 2 virginie.galindo 2016-05-23 21:01:39 +0000 The bug has been transferred to github https://github.com/w3c/webcrypto/issues/25 with the directive to implement the suggested change by Eric and backed by Jim. 126493 3 watsonm 2016-05-23 22:56:14 +0000 Moved to https://github.com/w3c/webcrypto/issues/33