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 19705 - Default value of keyUsage is not very useful
Summary: Default value of keyUsage is not very useful
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Mark Watson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-25 18:17 UTC by Mark Watson
Modified: 2014-01-25 00:23 UTC (History)
3 users (show)

See Also:

Attachments

Description Mark Watson 2012-10-25 18:17:40 UTC 
The default value of the keyUsage parameter to the createKeyGenerator and createKeyDeriver methods is an empty list: not very useful.

In practice this means all parameters must always be specified, meaning there is little point in specifying default values for any of them.

Either:
a) A more useful default (such as [ "encrypt", "decrypt", "sign", "verify" ]) should be specified
b) keyUsage should be moved ahead of the other parameters, with no default specified
c) no defaults should be specified for any of the parameters
Comment 1 Alexey Proskuryakov 2013-11-01 17:57:02 UTC 
It would be nice to have this addressed. The current function signatures are quite misleading and confusing.
Comment 2 Mark Watson 2014-01-22 23:40:00 UTC 
I propose we remove the defaults