W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: JS crypto?

From: Jeremy Orlow <jorlow@chromium.org>
Date: Wed, 12 May 2010 17:18:30 +0100
Message-ID: <AANLkTilOjr1FkHKvdUzvtHFRmsijJ7oNUxlWnrNhKD_N@mail.gmail.com>
To: nathan@webr3.org
Cc: public-webapps <public-webapps@w3.org>
This came up not too long ago in the context of persistent storage.  The
verdict (IIRC) was that we're not interested in adding crypto just to
the persistent storage APIs, but that we might be interested in adding a
general crypto API.

Does anyone have any data for how widely used window.crypto and/or JS
library alternatives are?  If they aren't widely used, maybe it's worth
seeing if we can find use cases for crypto in the browser that aren't
satisfied by JS libraries?

To answer your question, I'm not aware of any existing standardization
efforts, but I think the time might be right to explore the possibility.

J


On Wed, May 12, 2010 at 5:09 PM, Nathan <nathan@webr3.org> wrote:

> Hi All,
>
> Unsure if this is the best place to ask, but is there currently any JS (or
> user agent) support for cryto functions such as sign/seal/encrypt/decrypt?
>
> Perhaps a working group, a draft, anything?
>
> I would be very keen to see crypto support in all the browsers standardized
> and methods exposed to JS.
>
> For instance, if you have your public key on the web somewhere, I should be
> able to seal a document using it, publish it on the web, and know that if
> you visit that uri in your browser that it will decrypt it using the private
> key from a certificate you have installed in the browser.
>
> Best & thanks in advance for any response,
>
> ps: aware of window.crypto in firefox/gecko
>
> Nathan
>
>
Received on Wednesday, 12 May 2010 16:19:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:38 GMT