Chrome should be able to generate certs

[wiki.git] / doc / enabling_client_certificate_auth_in_chrome.html

diff --git a/doc/enabling_client_certificate_auth_in_chrome.html b/doc/enabling_client_certificate_auth_in_chrome.html
index 697348fd140994c368a43b0a174b45db3f1ef2fa..2e47958ffa5f97138aa6642a2bac0257c8580954 100644 (file)
--- a/doc/enabling_client_certificate_auth_in_chrome.html
+++ b/doc/enabling_client_certificate_auth_in_chrome.html
@@ -11,9 +11,7 @@ to install libnss3-tools, then run "certutil -d sql:$HOME/.pki/nssdb -A -t
 "C,," -n <certificate nickname> -i <certificate filename>" for both the MIT CA
 and (if you want it) the CSAIL CA.</p>
 
 "C,," -n <certificate nickname> -i <certificate filename>" for both the MIT CA
 and (if you want it) the CSAIL CA.</p>
 

-<p>The easiest way to install a client cert in the nss database is simply to
-install it on Firefox; at that point, it should be in the list of certificates
-you get when you run "certutil -d sql:$HOME/.pki/nssdb -L".  If not, go back to
+<p>Recent Linux builds should be able to generate certificates via the usual web interface, however there will be no UI feedback in doing so. Failing that, the easiest way to install a client cert in the nss database is simply to install it on Firefox; at that point, it should be in the list of certificates you get when you run "certutil -d sql:$HOME/.pki/nssdb -L".  If not, go back to

 the LinuxCertManagement page and do it manually.</p>
 
 <p>Here's the last key to the puzzle: Chrome on Linux currently lacks a UI for selecting a certificate, so run it with the --auto-ssl-client-auth flag. Enabling this flag configures Chrome to automatically send an certificate to websites without prompting, as Firefox will do under certain configurations. This is considered a privacy issue; see UI notes #3 in the Chromium <a href="http://dev.chromium.org/developers/design-documents/ssl-client-authentication">design document</a> and the linked <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=295922">Mozilla bug</a>. Bug <a href="http://code.google.com/p/chromium/issues/detail?id=25241">#25241</a> tracks this issue in Chrome on Linux.</p>
 the LinuxCertManagement page and do it manually.</p>
 
 <p>Here's the last key to the puzzle: Chrome on Linux currently lacks a UI for selecting a certificate, so run it with the --auto-ssl-client-auth flag. Enabling this flag configures Chrome to automatically send an certificate to websites without prompting, as Firefox will do under certain configurations. This is considered a privacy issue; see UI notes #3 in the Chromium <a href="http://dev.chromium.org/developers/design-documents/ssl-client-authentication">design document</a> and the linked <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=295922">Mozilla bug</a>. Bug <a href="http://code.google.com/p/chromium/issues/detail?id=25241">#25241</a> tracks this issue in Chrome on Linux.</p>