<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add features requested by 1Password to WebCrypto"
href="https://bugs.webkit.org/show_bug.cgi?id=151125#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add features requested by 1Password to WebCrypto"
href="https://bugs.webkit.org/show_bug.cgi?id=151125">bug 151125</a>
from <span class="vcard"><a class="email" href="mailto:rob@agilebits.com" title="Rob <rob@agilebits.com>"> <span class="fn">Rob</span></a>
</span></b>
<pre>Just to update here, Jiewen Tan's recent work to update `importKey` to the latest spec (<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Update SubtleCrypto::importKey to match the latest spec"
href="show_bug.cgi?id=164446">https://bugs.webkit.org/show_bug.cgi?id=164446</a>) fixes half of our (1Password's) problems with WebKit. In the latest WebKit nightly, it's now possible to sign in to accounts that were created with RSA-OAEP-256 keys. The biggest remaining issue here without a workaround is fixing `exportKey` <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebCrypto can generate but fails to export RSA-OAEP-256 keys"
href="show_bug.cgi?id=156114">https://bugs.webkit.org/show_bug.cgi?id=156114</a>. AES-GCM would be great too so we can avoid polyfilling it (<a class="bz_bug_link
bz_status_NEW "
title="NEW - WebCrypto API support for AES-GCM"
href="show_bug.cgi?id=157175">https://bugs.webkit.org/show_bug.cgi?id=157175</a>).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>