(no commit message)

[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 7c5e8e4e5355994d147480517aa601aff276a51d..f0161cde736c6577d8d5ec3ea007ec01438fcdfa 100644 (file)
--- a/doc/enabling_client_certificate_auth_in_chrome.html
+++ b/doc/enabling_client_certificate_auth_in_chrome.html
@@ -6,7 +6,7 @@
 
 <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>