This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When you call crypto.subtle.generateKey() extractable=false and it results in a keypair. Should both the public key and private key receive extractable=false, or should the public key implicitly be extractable=true?
+1 to addressing this in one way or another. Should generateKey() even have the extractable argument? I realize that it provides for behavior that can't be achieved otherwise, but I'm not sure if generateKey is part of any real use cases that exist for extractable=false.
This looks like a duplicate of bug 23013.
*** This bug has been marked as a duplicate of bug 23013 ***