W3C home > Mailing lists > Public > public-webid@w3.org > May 2014

Re: Releasing RWW.IO

From: Tim Holborn <timothy.holborn@gmail.com>
Date: Sat, 3 May 2014 18:24:01 +1000
Cc: Andrei Sambra <andrei.sambra@gmail.com>, public-webid <public-webid@w3.org>, "public-rww@w3.org" <public-rww@w3.org>
Message-Id: <484B26B4-2596-43F0-AC59-98DE6E5BA08D@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
WebID TLS certs may need browser support in future, but, im betting if the method works, itll likely get that browser support (one way or another). 

It does not provide an entire solution however, it is simply a constituent of a solution IMHO.

If youd done enough testing, youd have too many WebID Certificates. Right-up until the point, where you set-up your own cert; manage it effectively, which in-turn means you only need one Cert

Ive still not sorted that out yet.

i think perhaps a back-up (or export) button on RWW.io might be a good idea, somewhere in the todo list.

timh.

On 3 May 2014, at 6:08 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:

> Now I have tried it out as well including the micro-blogging.
> It was cool with one exception, TLS CCA (Client Certificate Authentication)
> 
> Logging in to http://cimba.co required me to select certificate twice and
> from a pretty long list of non-WebID certificates.
> 
> Unless W3C gets their act together and creates a web-compliant replacement
> for TLS CCA, WebID won't ever catch on.  I have no faith in W3C for taking
> any action on this since not even the requirements have ever been discussed.
> TLS is a sacred cow.
> 
> Fortunately Google hadn't any problems slaughtering this poor creature
> when they started their U2F project which have created a hype I haven't
> seen before during my 15Y+ in the "id-business".  It didn't take an
> eternity either.
> 
> Anders
> grumpy old fart with a mission
> 
> 
Received on Saturday, 3 May 2014 08:25:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:55 UTC