But anyway, no need to use <a> --- id works

[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 c04377842a08b58d37d17f39035a7fe88e8ca7b2..8ba32ecc02dfa5ea0c25a352dfff8382776e218d 100644 (file)
--- a/doc/enabling_client_certificate_auth_in_chrome.html
+++ b/doc/enabling_client_certificate_auth_in_chrome.html
@@ -6,7 +6,7 @@ As far as I know, this only works with the daily build from the chromium-daily p
 if you're running Debian or Ubuntu, you can add "deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu karmic main" to your
 /etc/apt/sources.list and then apt-get update 
 </p>
-<h3><a name="getting_certs">Installing Certificates</a></h3>
+<h3 id="getting_certs">Installing Certificates</h3>
 <p> The simplest thing to do is go to the <a href="https://ca.mit.edu/ca/">usual web interface</a> and follow the instructions to install certs normally. 
 You may also want the <a href="http://ca.csail.mit.edu/cacert">CSAIL CA</a> (specifically, the Master CA).
 If this works, you should be able to skip to telling chrome to<a href="#using_certs">use certtificate by default</a>
@@ -21,7 +21,7 @@ to install libnss3-tools, then run "certutil -d sql:$HOME/.pki/nssdb -A -t
 "C,," -n  -i " for both the MIT CA and (if you want it) the CSAIL CA.</p>
 <!--what do you pass as argumets exactly? -->
 
-<h3><a name="using_certs">Using Certificates</a></h3>
+<h3 id="using_certs">Using Certificates</h3>
 <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.<p>
 To do this by default in Gnome, you want to edit both Preferred Applications and the Main Menu entry 
 this way links you click on outside of Chrome open this way.  (Gnome Do and similar pull their data from Main Menu, among other places.)