151308 2015-11-16 08:49:15 -0800 Not possible to import RSA-OAEP keys with hash: {name: "SHA-256"} 2016-11-10 12:27:03 -0800 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=164446 InRadar P2 Normal --- 160894 1 roustem webkit-unassigned ap bfulgham jiewen_tan piotr rob webkit-bug-importer oldest_to_newest 1142234 0 roustem 2015-11-16 08:49:15 -0800 When trying to import RSA-OAEP private key with hash parameter == SHA-256, the result uses SHA-1 instead. IMPORTING KEY: Uint8Array [123, 34, 97, 108, 103, 34, 58, 34, 82, 83, …] Object hash: {name: "SHA-256"} modulusLength: 2048 name: "RSA-OAEP" publicExponent: Uint8Array [1, 0, 1] IMPORTED KEY: algorithm: {name: "RSA-OAEP", modulusLength: 2048, publicExponent: Uint8Array [1, 0, 1], hash: {name: "SHA-1"}} extractable: true type: "private" usages: ["decrypt"] 1142439 1 ap 2015-11-16 18:49:15 -0800 Yes, the older version of WebCrypto spec that WebKit currently implements didn't take a hash when importing, so SHA-256 here is just ignored. We also don't support the RSA-OAEP-256 JWK algorithm yet. 1210221 2 webkit-bug-importer 2016-07-12 16:05:36 -0700 <rdar://problem/27311678> 1221425 3 rob 2016-08-19 12:22:28 -0700 I keep scanning the Safari TP release notes in hopes that I'll see some progress on this. Safari is still unsupported for many 1Password customers who created accounts last year using Chrome or Firefox, which support RSA-OAEP-256. 1249913 4 jiewen_tan 2016-11-10 12:26:46 -0800 The bug is resolved by Bug 164446.