W3C home > Mailing lists > Public > public-webid@w3.org > April 2016

Re: (Pre-)Intent to Deprecate: <keygen> element and application/x-x509-*-cert MIME handling

From: Henry Story <henry.story@gmail.com>
Date: Fri, 8 Apr 2016 21:41:05 +0100
Cc: Read-Write-Web <public-rww@w3.org>, public-webid <public-webid@w3.org>
Message-Id: <87B4FAAA-D574-4A1B-8190-6086B69DE8BE@gmail.com>
To: Jonas Smedegaard <dr@jones.dk>

> On 8 Apr 2016, at 21:21, Jonas Smedegaard <dr@jones.dk> wrote:
> 
> Quoting Melvin Carvalho (2015-07-30 18:01:41)
>> WebID is still nascent, and readily admits it won't work with Edge. An 
>> alternative would be for WebID to proceed with standards that are 
>> actually widely used and have a viable chance at being usable - such 
>> as WebCrypto.

That of course works too using Http-Signature which I have implemented on the client
and server here:
https://github.com/solid/solid-spec/issues/52

Web Crypto has problems with not being tied into chrome though, and a few
other limitations.  It would probably be worth enhancing WebID-TLS definition 
so that it can work  seamlessly with both.

My rww-play server actually does that.

Henry

> 
> Debian has introduced the use of client-side cert recently for its 
> single-sign-on services.  Might be interesting to follow that: 
> https://wiki.debian.org/DebianSingleSignOn
> 
> E.g. notice the brand new addition on workarounds for Chrome/Chromium 
> added today: 
> https://wiki.debian.org/DebianSingleSignOn?action=diff&rev2=72&rev1=70
> 
> 
> - Jonas
> 
> -- 
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> 
> [x] quote me freely  [ ] ask before reusing  [ ] keep private
Received on Friday, 8 April 2016 20:41:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:06:00 UTC