This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23695 - Clarify how "extractable" applies to keypairs
Summary: Clarify how "extractable" applies to keypairs
Status: RESOLVED DUPLICATE of bug 23013
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-31 22:28 UTC by Eric Roman
Modified: 2014-02-20 21:14 UTC (History)
2 users (show)

See Also:

Attachments

Description Eric Roman 2013-10-31 22:28:16 UTC 
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?
Comment 1 Alexey Proskuryakov 2013-11-08 22:45:04 UTC 
+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.
Comment 2 Alexey Proskuryakov 2013-11-08 22:51:50 UTC 
This looks like a duplicate of bug 23013.
Comment 3 Mark Watson 2014-02-20 21:14:21 UTC 

*** This bug has been marked as a duplicate of bug 23013 ***