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 24768 - Should RsaKeyAlgorithm.publicExponent be an array instead of BigInteger?
Summary: Should RsaKeyAlgorithm.publicExponent be an array instead of BigInteger?
Status: RESOLVED DUPLICATE of bug 25626
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-21 19:03 UTC by Eric Roman
Modified: 2014-05-12 04:55 UTC (History)
0 users

See Also:

Attachments

Description Eric Roman 2014-02-21 19:03:49 UTC 
For starters, RsaKeyAlgorithm.publicExponent should be readonly (bug 24767)

However even after this is done, I believe the BigInteger (which is an ArrayBufferView) would still be mutable. So programmers could change the value of the publicExponent (however this wouldn't be expected to actually affect the key).

WebIDL defines a readonly array as being fixed and immutable, so that may be a better fit (If I am interpreting WebIDL correctly).

Cheers.
Comment 1 Ryan Sleevi 2014-05-12 04:55:49 UTC 
The resolution of Bug 25626 will see this as invalid, in that it will return an object rather than an interface.

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