151125 2015-11-10 19:44:30 -0800 Add features requested by 1Password to WebCrypto 2017-01-03 14:35:19 -0800 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 157175 https://bugs.webkit.org/show_bug.cgi?id=157175 https://twitter.com/ryosukeniwa/status/664286585593049088 InRadar P2 Normal --- 160880 1 rniwa webkit-unassigned ap bfulgham elima jiewen_tan mail oliver rob roustem oldest_to_newest 1141036 0 rniwa 2015-11-10 19:44:30 -0800 The list of features being requested: https://gist.github.com/roustem/5113d48e1a91e220ff6d It looks like they need at least AES-GCM. 1141040 1 ap 2015-11-10 20:04:02 -0800 rdar://problem/23379153 1156225 2 roustem 2016-01-16 14:28:05 -0800 We polyfilled AES-GCM using SCJL in 1Password. The biggest show stopper is RSA-OAEP-256. 1177595 3 mail 2016-03-23 20:50:35 -0700 I'm currently implementing AES-GCM support for OpenPGP.js (IETF draft): https://github.com/openpgpjs/openpgpjs/pull/430 Having native support in WebKit would make a big difference for larger files on iOS: https://github.com/openpgpjs/openpgpjs/pull/430#issuecomment-200469142 I'd happily help with testing if I can. Thanks for your consideration! 1250355 4 rob 2016-11-11 13:01:59 -0800 Just to update here, Jiewen Tan's recent work to update `importKey` to the latest spec (https://bugs.webkit.org/show_bug.cgi?id=164446) 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` https://bugs.webkit.org/show_bug.cgi?id=156114. AES-GCM would be great too so we can avoid polyfilling it (https://bugs.webkit.org/show_bug.cgi?id=157175). 1263552 5 jiewen_tan 2017-01-03 14:35:19 -0800 Duplicate this bug to Bug 157175 since the only remaining request from 1Password is to add AES-GCM. *** This bug has been marked as a duplicate of bug 157175 ***