Re: Key Opacity/Identification Issue - Web Cryptography Charter Updated from Anders Rundgren on 2011-12-11 (public-identity@w3.org from December 2011)

From: Anders Rundgren <anders.rundgren@telia.com>
Date: Sun, 11 Dec 2011 09:47:48 +0100
To: Tom Ritter <tom@ritter.vg>
CC: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Harry Halpin <hhalpin@w3.org>, "public-identity@w3.org" <public-identity@w3.org>
Message-ID: <4EE46E34.1040800@telia.com>

On 2011-12-11 05:37, Tom Ritter wrote:
<snip>
>  - A way to expose parameters about the underlying connection to a
> higher-level protocol (e.g. certificates and chain in javascript
> parameters)

> The last bullet point I mentioned is something I've been pushing for a
> bit.  Especially coupled w/ signing and verifying javascript libraries
> - you can implement key pinning and a number of interesting CA
> auditing and verification tools if you can read the supplied
> certificate parameters.

+1

Anders

Received on Sunday, 11 December 2011 08:55:33 UTC