I think there needs to be a dot after the -d in the code to run for Ubuntu/Debian...

[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 fa7d1f65f856326a261cf3a1bd0a27438d537a4a..7c5e8e4e5355994d147480517aa601aff276a51d 100644 (file)
--- a/doc/enabling_client_certificate_auth_in_chrome.html
+++ b/doc/enabling_client_certificate_auth_in_chrome.html
@@ -6,13 +6,13 @@
 
 <p>On Linux, however, Mozilla Firefox uses a private certificate store instead of the system <a href="http://www.mozilla.org/projects/security/pki/nss/">NSS</a> one. There is no system interface for adding certificates, and Chromium has not implemented certificate manager on Linux yet. You may star Chromium bug <a href="http://code.google.com/p/chromium/issues/detail?id=19991">#19991</a> to be informed of progress. In the meantime, you may use the NSS command-line tools to manage your certificates. If you're running Ubuntu or Debian, install the package <tt>libnss3-tools</tt>. To trust the MIT CA for SSL, download the file and run</p>
 
 
 <p>On Linux, however, Mozilla Firefox uses a private certificate store instead of the system <a href="http://www.mozilla.org/projects/security/pki/nss/">NSS</a> one. There is no system interface for adding certificates, and Chromium has not implemented certificate manager on Linux yet. You may star Chromium bug <a href="http://code.google.com/p/chromium/issues/detail?id=19991">#19991</a> to be informed of progress. In the meantime, you may use the NSS command-line tools to manage your certificates. If you're running Ubuntu or Debian, install the package <tt>libnss3-tools</tt>. To trust the MIT CA for SSL, download the file and run</p>
 

-<blockquote><code>certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "MIT CA" -i path/to/mitca.crt</code></blockquote>
+<blockquote><code>certutil -d. sql:$HOME/.pki/nssdb -A -t "C,," -n "MIT CA" -i path/to/mitca.crt</code></blockquote>

 
 <p>For more information, visit Google's page on <a href="http://code.google.com/p/chromium/wiki/LinuxCertManagement">Linux certificate management</a> and Mozilla's documentation on <a href="http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html"><tt>certutil</tt></a>.</p>
 
 <h3>Enrolling in and Using Client Certificates</h3>
 
 
 <p>For more information, visit Google's page on <a href="http://code.google.com/p/chromium/wiki/LinuxCertManagement">Linux certificate management</a> and Mozilla's documentation on <a href="http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html"><tt>certutil</tt></a>.</p>
 
 <h3>Enrolling in and Using Client Certificates</h3>
 

-<p>As of Chrome 6, the standard workflows should work without workarounds. Visit the usual <a href="https://ca.mit.edu/ca/">usual web interface</a> and follow the instructions to install certs normally. You can check your work with <a href="https://scripts-cert.mit.edu/~geofft/demo/detect.php">this demo page</a>.  If everything is working, it should welcome you by name, and tell you that a certificate for your username is installed.</p>
+<p>As of Chrome 6, the standard workflows should work without workarounds. Visit the usual <a href="https://ca.mit.edu/ca/">usual web interface</a> and follow the instructions to install certs normally. Note that, until Chrome 7, there is not yet any UI feedback for the enrollment. It should, however, work. You can check your work with <a href="https://scripts-cert.mit.edu/~geofft/demo/detect.php">this demo page</a>.  If everything is working, it should welcome you by name, and tell you that a certificate for your username is installed.</p>

 
 <h3>Using a Smart Card or Other Password-Protected Certificate Store</h3>
 
 
 <h3>Using a Smart Card or Other Password-Protected Certificate Store</h3>