W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

[WebCrypto.Next] Any ideas on how to proceed?

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Wed, 18 Feb 2015 07:30:48 +0100
Message-ID: <54E43198.8040305@gmail.com>
To: "public-web-security@w3.org" <public-web-security@w3.org>
CC: public-webapps <public-webapps@w3.org>
As you probably noted, all proposals related to
were shot down.

Are we waiting on something, and if so is the case, exactly what?

Is the idea of building on an already semi-established solution like Chrome Native Messaging unacceptable?

Or should this disparate community rather standardize on U2F?

Another solution (IMO "workaround") is using local services supplying "Security Services" through Redirects, XHR or WebSockets.

Since the (in)famous plugins were simply removed without any thoughts of the implications, it seems that the browser vendors currently "own" this question.

Received on Wednesday, 18 February 2015 06:31:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC