- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 May 2014 08:38:04 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25387 --- Comment #6 from Ryan Sleevi <sleevi@google.com> --- (In reply to Anne from comment #5) > The main problem I think is that you want a bigint, and are inventing one on > top of a Uint8Array. Ideally there would at least be some coordination with > TC39 so that they know this is going on. This isn't really accurate, for the reasons explained on https://github.com/w3ctag/spec-reviews/issues/3#issuecomment-41630590 This WG has spent a lot of time debating BigInteger - whether it's a first class type or not. You can see in the archives a previous proposal by Microsoft during the eBay/PayPal F2F that demonstrated a number of problems with trying to describe BigInteger for cryptographic operations. As explained during the W3C TAG review, the typedef here is to annotate a binary format (akin to the ASN.1 DER-encoding of SPKI/PKCS#8) If you're performing cryptographic operations using these, then we've failed as a WG. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 12 May 2014 08:38:06 UTC