fix: for MSRCrypto 1.6.0

Since MSRCrypto is a viable option for a falback,
it must be usable.

These differ from the WebCrypto API
* The algorithm argument in importKey is passed through to the imported key.
* The algorithm is normalize to lower case

microsoft/MSR-JavaScript-Crypto#1

Author: seebees

modules/material-management-browser/src/material_helpers.ts

@@ -262,11 +262,11 @@ export async function _importCryptoKey<T extends WebCryptoMaterial<T>> (
      * with browsers that need a zero byte gcm fallback.
      */
     const format = 'raw'
-    const algorithm = suite.kdf
+    const algorithm = { name: suite.kdf, length: suite.keyLength }
     return subtle.importKey(format, udk, algorithm, extractable, keyUsages)
   } else {
     const format = 'jwk'
-    const algorithm = suite.encryption
+    const algorithm = { name: suite.encryption, length: suite.keyLength }
     const jwk = bytes2JWK(udk)
     return subtle.importKey(format, jwk, algorithm, extractable, keyUsages)
   }

modules/material-management/src/cryptographic_material.ts

@@ -608,11 +608,18 @@ export function isValidCryptoKey<T extends WebCryptoMaterial<T>> (
   // @ts-ignore length is an optional value...
   const { name, length } = algorithm
 
+  /* MSRCrypto, for legacy reasons,
+   * normalizes the algorithm name
+   * to lower case.
+   * https://github.com/microsoft/MSR-JavaScript-Crypto/issues/1
+   * For now, I'm going to upper case the name.
+   */
+
   // Only symmetric algorithms
   return type === 'secret' &&
     // Must match the suite
-    ((kdf && name === kdf) ||
-     (name === encryption && length === keyLength)) &&
+    ((kdf && name.toUpperCase() === kdf) ||
+     (name.toUpperCase() === encryption && length === keyLength)) &&
     /* Only valid usage are: encrypt|decrypt|deriveKey
      * The complexity between deriveKey and suite.kdf should be handled in the Material class.
      */