Re: [foaf-dev] Re: RDFAuth: an initial sketch

Hi Toby, sorry I missed your previous post. I need to study HTTPS more  
which is why I could not grok it at the time.
I have added a link to both posts in the "history" section of http://blogs.sun.com/bblfish/entry/rdfauth_sketch_of_a_buzzword

Here is your previous post:
    http://www.w3.org/mid/62649.81.2.120.180.1206622777.squirrel@goddamn.co.uk

Let me study it now.

	Henry


On 1 Apr 2008, at 12:40, Toby A Inkster wrote:
>
> Story Henry wrote:
>
>> My feeling is that what is needed is to see how this could be made to
>> work better with SSL.
>
> I've already posted a message suggesting an HTTPS-based solution.
>
>  Message-ID: <62649.81.2.120.180.1206622777.squirrel@goddamn.co.uk>
>  Subject: Re: [foaf-dev] Re: privacy and open data
>  Date: Thu, 27 Mar 2008 12:59:37 -0000 (UTC)
>
> Summary:
>
> 1. Client requests public FOAF
> 2. FOAF contains rdf:seeAlso with URI for HTTPS private FOAF
> 3. Client requests private FOAF using a client-side SSL cert
> 4. Client includes URI of their public FOAF in HTTP "From" header
> 5. HTTPS server requests client's public FOAF file and queries it
>    to find client's certificate serial number
> 6. Server checks that FOAF serial number matches the request
>    cert serial number, thus requesting client really does own
>    the FOAF file in HTTP From header
> 7. Server makes decision on what information client should be
>    shown, based on client's FOAF, and on client's FOAF URI
> 8. Server sends client this information as RDF
>
> -- 
> Toby A Inkster BSc (Hons) ARCS
> [Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
> [OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 5 days, 21:52.]
>
>                           Cognition 0.1 Alpha 6
>         http://tobyinkster.co.uk/blog/2008/03/29/cognition-alpha6/
>