- From: Aymeric Vitte <vitteaymeric@gmail.com>
- Date: Mon, 13 May 2013 19:49:40 +0200
- To: Anders Rundgren <anders.rundgren@telia.com>
- CC: Arun Ranganathan <arun@mozilla.com>, Ryan Sleevi <sleevi@google.com>, "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
I have suggested too : http://lists.w3.org/Archives/Public/public-webcrypto/2013May/0070.html To be more clear, only a combination of link above and links below is feasible, and that's not a hack, neither a hook, that's the web. And I believe "super cookie" is not the web, but you can consider indexedDB as a mega cookie. I have not thought a lot to eID case, maybe a more detailed example including requirements/restrictions could help to try writing it and see if it's feasible as such. Regards, Le 13/05/2013 19:32, Arun Ranganathan a écrit : > On May 13, 2013, at 1:00 PM, Ryan Sleevi wrote: > >> That question has already been answered. > > The issue of cross-origin use of cryptographic interfaces is discussed here: > > http://lists.w3.org/Archives/Public/public-webcrypto/2013May/0036.html > > And Aymeric has suggested: > > http://lists.w3.org/Archives/Public/public-webcrypto/2013May/0067.html > > My opinion is that this API is constrained by this type of use. Use cases that fall out of this type of use honestly fall beyond the scope of the Web Crypto API. > > -- A* -- jCore Email : avitte@jcore.fr iAnonym : http://www.ianonym.com node-Tor : https://www.github.com/Ayms/node-Tor GitHub : https://www.github.com/Ayms Web : www.jcore.fr Webble : www.webble.it Extract Widget Mobile : www.extractwidget.com BlimpMe! : www.blimpme.com
Received on Monday, 13 May 2013 17:47:31 UTC