- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 18 May 2014 11:04:48 -0400
- To: public-webid@w3.org
- Message-ID: <5378CC10.9040102@openlinksw.com>
On 5/18/14 2:54 AM, Anders Rundgren wrote: > This limitation has been discussed in various W3C forums for at least two years. > As far as I know*none* of the browser vendors have ever commented on this. > > To me that says: The browser vendors do not care about HTTPS CCA (Client > Certificate Authentication) at all. > > Hoping for improvements in HTTPS CCA is a pure waste of time; it is better > start playing with other authentication technologies. There are such. > > Anders For the last time, Browsers are evolving. You only have Chrome and Opera at this time that suffer from the problem you continue to recycle, somewhat inaccurately. Here is a simple service [1] that proves my point, all you have to do is open it using various browsers and then attempt to authenticate using different certificates. [1] http://id.myopenlink.net/ods/webid_demo.html -- IE (Windows), Safari (Mac OS X and iOS), Firefox (via its Javascript approach) all work fine. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Sunday, 18 May 2014 15:05:18 UTC