W3C home > Mailing lists > Public > public-webid@w3.org > September 2012

Re: Perceived issues with TLS Client Auth

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 27 Sep 2012 07:54:40 -0400
Message-ID: <50643E80.30007@openlinksw.com>
To: public-webid@w3.org, Ben Laurie <benl@google.com>
On 9/27/12 5:35 AM, Ben Laurie wrote:
>     1. Through TLS his server knows that I have the private key of the
>     public key in the certificate.
>     2. The verification of the WebID is then done by follwing the
>     procedure described here
>     http://www.w3.org/2005/Incubator/webid/spec/#verifying-the-webids
> Right - so the steps you missed are where the WebID profile gets 
> updated to include the new key, and where joe.name <http://joe.name> 
> somehow (how?) decides that this WebID is allowed to log in...
Adding new relationships to profile documents is trivial. Each time you 
generate a new certificate simply add triples to the profile document 
reference by the WebID that watermarks the generated cert.

You can do this by hand i.e., mount you turtle document, edit, and save.

You can exploit a tool that does this for you.

I've demonstrated all of the above for a very long time. It just works.

The only challenge is getting folks to step back and grok what Linked 
Data enables. Once understood, the ingenuity and power of WebIDs becomes 
crystal clear. There is much more to the architecture of the Web than 
95% of its users exploit or understand. There's a reason why many of us 
are so passionate about this stuff :-)



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Thursday, 27 September 2012 11:55:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:35 UTC