[webcrypto] Add deriveBits key_op to JWK import/export.

content/child/webcrypto/shared_crypto_unittest.cc

Index: content/child/webcrypto/shared_crypto_unittest.cc
diff --git a/content/child/webcrypto/shared_crypto_unittest.cc b/content/child/webcrypto/shared_crypto_unittest.cc
index 3beadc476170cd9b88ad1d7204d2ec19bf300580..005b32ef0d4cec580b040580557ff96fc89eb045 100644
--- a/content/child/webcrypto/shared_crypto_unittest.cc
+++ b/content/child/webcrypto/shared_crypto_unittest.cc
@@ -1185,7 +1185,6 @@ TEST_F(SharedCryptoTest, ImportJwkKeyUsage) {
     const blink::WebCryptoAlgorithm algorithm;
     const blink::WebCryptoKeyUsage usage;
   };
-  // TODO(padolph): Add 'deriveBits' key_ops value once it is supported.
   const TestCase test_case[] = {
       {"encrypt", "A128CBC", aes_cbc_algorithm,
        blink::WebCryptoKeyUsageEncrypt},
@@ -1197,7 +1196,9 @@ TEST_F(SharedCryptoTest, ImportJwkKeyUsage) {
       {"unwrapKey", "A128KW", aes_kw_algorithm,
        blink::WebCryptoKeyUsageUnwrapKey},
       {"deriveKey", "HS256", hmac_algorithm,
-       blink::WebCryptoKeyUsageDeriveKey}};
+       blink::WebCryptoKeyUsageDeriveKey},
+      {"deriveBits", "HS256", hmac_algorithm,
+       blink::WebCryptoKeyUsageDeriveBits}};

[Ryan Sleevi, 2014/05/09 00:06:03]

Hrm. Not sure if a spec bug or not that you can import HMAC keys that support
operations that the underlying algorithm does not...

[eroman, 2014/05/09 00:36:49]

It is not a spec bug, it is an implementation bug.

The spec says to fail such operations. Something I am going to work on next.

I will remove this then, since this isn't a valid long-term test

   for (size_t test_index = 0; test_index < ARRAYSIZE_UNSAFE(test_case);
        ++test_index) {
     SCOPED_TRACE(test_index);