Re: How to request a WebID?

What name will you choose? Will it mean any thing to 1 billion users in china? Will Russians object to the use of roman characters? Why cannot Thai folk see Thai style writing?

2 modern, professional choices:

Have all certs bear a common cert policy oid, with accompanying uri.

Have all certs bear an application policy oid , like 50 windows apps using https exploit to segment the https world into 50 variants of https - with different discovery/validation/revocation practices per appid.

Both suggestions require v3 certs, which hurts use of v1 certs.

In the v1 world, one played tricks. If the issuer name had rdn with oid of x.y.z do not display it (by definition) bur use it as a discriminatory. This was acceptable as the resolver indicated which rdns in the name were distinguished, and which were merely non security enforcing hints.

Make sure it works when non browser https clients are using webids (such as servers accessing sparql endpoints).


On Apr 5, 2011, at 6:31 AM, Henry Story <henry.story@bblfish.net> wrote:

> 
> On 5 Apr 2011, at 15:01, Nathan wrote:
> 
>> Hi All,
>> 
>> A possible issue, how does a server specifically tell a client that it's trying to auth with WebID?
> 
> This is ISSUE-15: Native browser-based WebID-only certificate display
> 
> (the name could do with improvement)
> 
>> 
>> Let's suppose for a moment that somebody else comes up with (or already uses) an authentication protocol which also uses client side certs as identifiers, let's call is SSL-ID.
>> 
>> In my browser I have 2 certificates, my WebID one, and my SSL-ID one, so:
>> 
>> 1) how does a server inform the client that it's requesting a WebID or an SSL-ID?
>> 2) how do I (as a user) know which to select, when all that's presented is a "please select your 
>> certificate"?
> 
> If all WebId enabled certificates that were self signed used the same DN then one could
> use the build in certificate selection mechanism of TLS
> 
> This was brought up here initially by Bruno Harbulot:
> http://lists.foaf-project.org/pipermail/foaf-protocols/2009-April/000450.html
> 
> It would require us to come up with such a DN, and for all WebID generated certificates to place those
> in the Certificates.
> 
> There is an issue of how this would be compatible with CA issued certs with WebIDs too. There we should perhaps recommend a TLS protocol improvement.
> 
>> 
>> We may need to address this, or include technologies which cater for this (I can't think of any off the top of my head, but then I haven't looked or paid attention to this use case yet - may follow up later if I find some).
>> 
>> Best,
>> 
>> Nathan
>> 
> 
> Social Web Architect
> http://bblfish.net/
> 
> 
>

Received on Tuesday, 5 April 2011 15:47:00 UTC