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 23013 - extractable and keyUsages under specified for Asymmetric algorithms
Summary: extractable and keyUsages under specified for Asymmetric algorithms
Status: RESOLVED FIXED
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:
: 23096 23695 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-08-19 21:59 UTC by jimsch
Modified: 2014-02-20 21:15 UTC (History)
3 users (show)

See Also:

Attachments

Description jimsch 2013-08-19 21:59:10 UTC 
The behavior of the extractable and keyUsages fields are underspecified when performing a key generation for asymmetric algorithms.  It should be explicitly stated that the extractable flag applies only to the private key that is generated.  It needs to be specified what happens when I pass in an array of keyUsages in terms of allocating them to the public and private keys.  I am assuming that this is the behavior that is desired, but if one passes in only public key keyUsge values, does that man that the private key keyUsage values should be mirrored or is the entire set assigned?
Comment 1 Eric Roman 2013-11-14 09:06:12 UTC 
*** Bug 23096 has been marked as a duplicate of this bug. ***
Comment 2 Mark Watson 2014-02-20 21:14:21 UTC 
*** Bug 23695 has been marked as a duplicate of this bug. ***
Comment 3 Mark Watson 2014-02-20 21:15:27 UTC 
I have specified that:
- the extractable attribute passed in applies only to the private key. Public keys are always extractable.
- each key receives the intersection of the usages that it supports and the usages that were specified in the method call