Re: Bi-directional certificate authentication [vs. passwords]
- From: Erwann Abalea <erwann@xxxxxxxxxx>
- Date: 17 Sep 2010 08:51:40 GMT
Le 16-09-2010, Tom St Denis <tom@xxxxxxx> a écrit :
On Sep 15, 2:54 pm, Paul Rubin <no.em...@xxxxxxxxxxxxxx> wrote:[...]
For general sites, maybe OpenID is closer to what you want.
Problem with OpenID is you still need to give private data to
*someone*.
OpenID can use TLS client authentication. Verisign proposes it.
But you're right, OpenID needs API changes on web server.
.
- Follow-Ups:
- Re: Bi-directional certificate authentication [vs. passwords]
- From: Tom St Denis
- Re: Bi-directional certificate authentication [vs. passwords]
- References:
- Re: Bi-directional certificate authentication [vs. passwords]
- From: Peter Gutmann
- Re: Bi-directional certificate authentication [vs. passwords]
- From: Tom St Denis
- Re: Bi-directional certificate authentication [vs. passwords]
- From: Paul Rubin
- Re: Bi-directional certificate authentication [vs. passwords]
- From: Tom St Denis
- Re: Bi-directional certificate authentication [vs. passwords]
- Prev by Date: Re: Bi-directional certificate authentication [vs. passwords]
- Next by Date: Re: Bi-directional certificate authentication [vs. passwords]
- Previous by thread: Re: Bi-directional certificate authentication [vs. passwords]
- Next by thread: Re: Bi-directional certificate authentication [vs. passwords]
- Index(es):