[Bug 29139] New: Allow specifying numbers in place of BigInteger?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29139

            Bug ID: 29139
           Summary: Allow specifying numbers in place of BigInteger?
           Product: Web Cryptography
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Web Cryptography API Document
          Assignee: sleevi@google.com
          Reporter: ericroman@google.com
                CC: public-webcrypto@w3.org
  Target Milestone: ---

This is feature request to re-define BigInteger from:
  typedef Uint8Array BigInteger;
To:
  typedef (unsigned long or Uint8Array) BigInteger


Motivation:

Often small valued numbers are passed in places that take a BigInteger.

For instance 65537 is a common value for publicExponent when generating RSA
keys. Currently callers need to express this as:

   publicExponent: new Uint8Array([0x01, 0x00, 0x01])

Whereas it would be simpler if they could write:

   publicExponent: 65537

This is strictly a convenience wrapper, as was added to some other WebCrypto
types.

This feature request was lifted from:
  https://github.com/w3c/webrtc-pc/issues/310

In which WebRTC has a spec bug where they use the simplified (unsupported)
syntax

In terms of compatibility, if this change were adopted by WebCrypto it would
not break existing usages of the API. However it would obviously cause problems
if support was not universal across implementations, since using the numeric
flavor might fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 22 September 2015 18:50:31 UTC