atom feed2 messages in org.foaf-project.lists.foaf-protocols[foaf-protocols] Google Chrome suppor...
FromSent OnAttachments
Story HenryMar 4, 2010 6:47 am 
Story HenryMar 8, 2010 1:48 am 
Subject:[foaf-protocols] Google Chrome support coming along
From:Story Henry (henr@bblfish.net)
Date:Mar 4, 2010 6:47:28 am
List:org.foaf-project.lists.foaf-protocols

In the latest build of Chrome [1] for OSX I was able to generate a client
certificate.

This is a result of the fix to bug 148 [2] "browser does not send valid
certification requests for creating SSL client certificates" which had been open
for 2 years.

But was not able to login to a web site. I am not sure yet where the issue that
remains to be fixed is. Perhaps issue 16831 [3] "Client SSL Certificate Support
for Mac" though it seems to be closed.

This is another bug/enhancement request I put up, no 29784 "User Interface
Improvement for Client Certificate Usage", which could be confusing because as
an enhancement request it may be beyond what they want to work on, and so they
may ignore the very real bug that does exist. They seem to think that the
KeyChain UI enabling the users to select which servers a certificate should be
used on is satisfactory.... Or at least worryingly close to thinking so.

Issue 36207 "Support SSL client authentication over renegotiation for Mac" may
be one of the major problems remaining. But I am not sure. Bruno?

Henry

[1] http://build.chromium.org/buildbot/snapshots/ [2] http://code.google.com/p/chromium/issues/detail?id=148 [3] http://code.google.com/p/chromium/issues/detail?id=16831 [4] http://code.google.com/p/chromium/issues/detail?id=29784 [5] http://code.google.com/p/chromium/issues/detail?id=36207

Social Web Architect http://bblfish.net/