- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 20 Jul 2014 22:43:13 -0400
- To: public-webid@w3.org
- Message-ID: <53CC7E41.2090607@openlinksw.com>
On 7/20/14 12:17 PM, henry.story@bblfish.net wrote: > On 20 Jul 2014, at 15:45, Anders Rundgren<anders.rundgren.net@gmail.com> wrote: > >> >On 2014-07-20 15:35,henry.story@bblfish.net wrote: >>> >> >>> >>On 20 Jul 2014, at 15:16, Anders Rundgren<anders.rundgren.net@gmail.com> wrote: >>> >> >>>> >>>Google scrapped established standards such as TLS CCA, ASN.1, PKCS #10, >>>> >>><keygen> and still got the entire industry (modulo Apple) backing them. >>> >> >>> >>keygen works fine for me on Chrome. Good developers work around problems, they >>> >>don't just complain. >> > >> >I'm not entirely alone: >> >http://lists.w3.org/Archives/Public/public-html/2009Sep/0043.html >> > >> >Naturally, Microsoft haven't published anything on what*they* consider the right solution. > The important thing is that it is in the html5 standard > > http://www.w3.org/TR/html5/forms.html#the-keygen-element > > With JavaScript you can easily work around the Microsoft exception by > calling their ActiveX extension. There was code published on the list here > to do this in the past. This is the kind of thing that could be documented > here more carefully. Volunteers to improve HOWTOs are welcome. > > > Henry, That suggestion is obsolete. IE knows how to work with multiple TLS sessions. It has a new session menu item, so working with different WebIDs is built-in. It has been so for years. Try it out. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: 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 Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 21 July 2014 02:43:35 UTC