W3C home > Mailing lists > Public > public-web-security@w3.org > May 2015

The updated WebCrypto charter

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Tue, 05 May 2015 18:56:06 +0200
Message-ID: <5548F626.1030306@gmail.com>
To: "public-web-security@w3.org" <public-web-security@w3.org>

The charter still talks about optional "Secondary API features".

Since these haven't been discussed in any detail isn't there an obvious risk that this could lead to a similar situation that we got with "WebCrypto.Next for Smart Cards"?  IMHO, hardly none of the listed items seem relevant these days either.  From the charter:

"control of TLS session login/logout":
Since the browser vendors with their emphasis on FIDO effectively have left HTTPS client certificate authentication "as is" (probably because it is considered clunky and privacy impeding), this is unlikely to happen.

"derivation of keys from TLS sessions":
I believe this more or less is already an IETF task: https://tools.ietf.org/wg/tokbind/

"a simplified data protection function":
I have no idea what that could be.

"multiple key containers":
Multiple providers have already been dismissed.  FIDO is also a strong candidate here.

"key import/export":
Is way too messy for ordinary users.

"a common method for accessing and defining properties of keys
  and the lifecycle control of credentials such enrollment, selection,
  and revocation of credentials with a focus enabling the selection of
  certificates for signing and encryption":
If we stick to domain-bound keys a la WebCrypto, IndexDB + https://pkijs.org/ provide this capability for the few that could be interested in PKI-solutions that only work for a single domain.

Platform-based keys such as featured in Microsoft's WebCrypto.Next proposal is an entirely different thing which squarely matches the WebCrypto API security model which also was a reason it didn't pull through.

It seems like a better deal waiting for possible V2 input after WebCrypto has actually hit the market and real use-cases.

Received on Tuesday, 5 May 2015 16:56:43 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 16 May 2015 00:34:03 UTC