24759 2014-02-21 01:08:20 +0000 Importing self-identifying keys 2014-03-13 02:22:58 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC All RESOLVED WONTFIX P2 normal --- 1 watsonm sleevi ap ericroman oldest_to_newest 101082 0 watsonm 2014-02-21 01:08:20 +0000 Presently, the algorithm whose import key operation is executed when importKey is called is determined entirely by the "algorithm" parameter to that method. For JWK, it would in theory be possible to support: P = crypto.subtle.importKey( "jwk", jwk, null, true, [ <usages> ] ) and have the correct algorithm determined by the "alg" member of the JWK. Do we want to support this ? 101085 1 sleevi 2014-02-21 02:10:23 +0000 Do we want to support this? No. SPKI is equally possible that it CAN be self-describing, but it is not GUARANTEED to be self-describing. "alg" is OPTIONAL in JWK. All that matters is kty. The API should ALWAYS require to specify the algorithm. 102285 2 ericroman 2014-03-13 01:35:20 +0000 If support for self-identifying JWK keys is not expected, then can we change the inputs to importKey() and unwrapKey() to make all parameters required? Currently: Promise<any> importKey(KeyFormat format, CryptoOperationData keyData, AlgorithmIdentifier? algorithm, boolean extractable, KeyUsage[] keyUsages ); Promise<any> unwrapKey(KeyFormat format, CryptoOperationData wrappedKey, Key unwrappingKey, AlgorithmIdentifier unwrapAlgorithm, AlgorithmIdentifier? unwrappedKeyAlgorithm, boolean extractable, KeyUsage[] keyUsages ); In particular, I am proposing the removal of the questionmark (nullable). Cheers 102287 3 watsonm 2014-03-13 02:22:58 +0000 Eric, you are right. I filed Bug 25036.