- From: Ryan Sleevi <sleevi@google.com>
- Date: Thu, 23 May 2013 10:01:16 -0700
- To: Nikos Mavrogiannopoulos <nikos.mavrogiannopoulos@esat.kuleuven.be>
- Cc: "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>, danny de cock <Danny.DeCock@esat.kuleuven.be>, Filipe Beato <filipe.beato@esat.kuleuven.be>
On Thu, May 23, 2013 at 1:44 AM, Nikos Mavrogiannopoulos <nikos.mavrogiannopoulos@esat.kuleuven.be> wrote: > This API allows for keys that are extractable meaning that the javascript > code would not just use the keys, but it will also transfer them to the > server or to another party. We see more possibilities for malicious usage of > this practice, than legitimate usage, so we propose to _not_ allow > extractable keys at all. > > > Thank you for your feedback. It is extremely unlikely your proposal will be integrated. Note that regardless of the "extractable" flag, Key objects support the Structured Clone algorithm, and can thus be shared between origins / parties via postMessage. This is a feature, not a bug. As mentioned in another message, it is an explicit non-goal of this API to "secure Javascript" independent of methods such as TLS, which appears to be the motivation for this proposal.
Received on Thursday, 23 May 2013 17:01:44 UTC