W3C home > Mailing lists > Public > public-webcrypto@w3.org > March 2013

Re: BigNum API Proposal

From: Richard Barnes <rbarnes@bbn.com>
Date: Mon, 4 Mar 2013 13:23:14 -0500
Cc: "'public-webcrypto@w3.org'" <public-webcrypto@w3.org>
Message-Id: <908800AE-26B2-4D0B-A4B6-DD7E2CF5FFDE@bbn.com>
To: Anthony Nadalin <tonynad@microsoft.com>
Could you clarify why this needs to be done as a web API instead of in JS?

To answer the obvious question: The WebCrypto API needs to provide crypto primitives so that the keying material can remain hidden from the JS in most circumstances.  Not clear to me that that applies to general BigNum stuff.


On Mar 4, 2013, at 12:41 PM, Anthony Nadalin <tonynad@microsoft.com> wrote:

> With all the discussion about blind signatures and support for BigNum, here is a draft API that Microsoft is submitting to the WG as a basis for the API. The BigNum API is common function in other JS libraries and a needed basic function for nonstandard algorithms. We would like to further discuss this at the up and coming F2F thus a heads up and a chance to read prior and looking forward to comments and discussions.
> <CryptoAPI.j_>
Received on Monday, 4 March 2013 18:23:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:15 UTC