- From: Mike Jones <Michael.Jones@microsoft.com>
- Date: Mon, 16 Jun 2014 23:42:24 +0000
- To: Ryan Sleevi <sleevi@google.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <4E1F6AAD24975D4BA5B16804296739439AD717E8@TK5EX14MBXC292.redmond.corp.microsoft.>
What’s the link to the current editor’s draft, Ryan? I’d like to have a look at these changes in situ. Thanks, -- Mike From: Ryan Sleevi [mailto:sleevi@google.com] Sent: Monday, June 16, 2014 4:32 PM To: public-webcrypto@w3.org Subject: New spec updates If you haven't noticed from the storm of Bugzilla updates, a new batch of Web Crypto updates are out - which will hopefully avoid further batching. https://dvcs.w3.org/hg/webcrypto-api/shortlog Notable improvements (note: these were all open bugs) - JWK-as-object, as discussed prior to LC, is specified - Algorithm normalization is now (hopefully) fully specified, and prior to asynchronous invocation - interface KeyAlgorithm is dead. Long live dictionary KeyAlgorithm (in response to TAG) - Lots of validation improvements on input parameters - ECDSA, ECDH - RSA-OAEP is now specified for handling SHA-2 algs - RSA-ES is gone - CryptoOperationData cloning is now fully defined (using ES6 terms) - Significantly reworked security considerations (thanks to everyone who contributed) On the editorial side, a number of consistency issues were fixed, although I still have a few bothering my obsessiveness. There are still 37 open bugs, although a few I'll be proposing to be closed as WontFix, with explanations, in follow-up
Received on Monday, 16 June 2014 23:43:46 UTC