- From: Nikos Mavrogiannopoulos <nikos.mavrogiannopoulos@esat.kuleuven.be>
- Date: Fri, 24 May 2013 15:55:53 +0200
- To: Ryan Sleevi <sleevi@google.com>
- Cc: <public-webcrypto-comments@w3.org>, danny de cock <danny.decock@esat.kuleuven.be>, Filipe Beato <filipe.beato@esat.kuleuven.be>
On 2013-05-23 18:57, Ryan Sleevi wrote: > This matches the existing APIs and cryptographic libraries in use by > browsers - which was a key use case in the chartering of this group > and design of this API - in that all parameters must be specified up > front so that an implementation can accurately represent whether an > operation is supported. > Implementations built on PKCS#11, for example (which include both > Firefox and Chromium) are not able to change IV midstream. I do not think that a new API designed in 2013 should contain the same issues and limitations as another API designed in 1995. Otherwise, why not just standardize the PKCS #11 API in javascript? regards, Nikos
Received on Friday, 24 May 2013 13:56:26 UTC