[html5] r8560 - [e] (0) Add some info about keygen. Affected topics: HTML

[whatwg at whatwg.org]

Author: ianh
Date: 2014-04-01 17:05:19 -0700 (Tue, 01 Apr 2014)
New Revision: 8560

Modified:
   complete.html
   index
   source
Log:
[e] (0) Add some info about keygen.
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2014-04-01 18:58:23 UTC (rev 8559)
+++ complete.html	2014-04-02 00:05:19 UTC (rev 8560)
@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 1 April 2014</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 2 April 2014</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -46273,7 +46273,9 @@
   It is expected that after receiving the <code><a href=#signedpublickeyandchallenge>SignedPublicKeyAndChallenge</a></code> (SPKAC)
   structure, the server will generate a client certificate and offer it back to the user for
   download; this certificate, once downloaded and stored in the key store along with the private
-  key, can then be used to authenticate to services that use TLS and certificate authentication.</p>
+  key, can then be used to authenticate to services that use TLS and certificate authentication. For
+  more information, see e.g. <a href=https://wiki.mozilla.org/CA:Certificate_Download_Specification>this MDN article</a>.</p>
+  <!-- or maybe https://developer.mozilla.org/en-US/docs/NSS_Certificate_Download_Specification ? -->
 
   <!-- how does the UA know which private key is associated with a certificate it gets back after
   the server has taken the public key created by <keygen> and turned it into a client cert? -->
@@ -104587,6 +104589,7 @@
   Henri Sivonen,
   Henrik Lied,
   Henry Mason,
+  Henry Story,
   Hugh Guiney,
   Hugh Winkler,
   Ian Bicking,

Modified: index
===================================================================
--- index	2014-04-01 18:58:23 UTC (rev 8559)
+++ index	2014-04-02 00:05:19 UTC (rev 8560)
@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 1 April 2014</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 2 April 2014</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -46273,7 +46273,9 @@
   It is expected that after receiving the <code><a href=#signedpublickeyandchallenge>SignedPublicKeyAndChallenge</a></code> (SPKAC)
   structure, the server will generate a client certificate and offer it back to the user for
   download; this certificate, once downloaded and stored in the key store along with the private
-  key, can then be used to authenticate to services that use TLS and certificate authentication.</p>
+  key, can then be used to authenticate to services that use TLS and certificate authentication. For
+  more information, see e.g. <a href=https://wiki.mozilla.org/CA:Certificate_Download_Specification>this MDN article</a>.</p>
+  <!-- or maybe https://developer.mozilla.org/en-US/docs/NSS_Certificate_Download_Specification ? -->
 
   <!-- how does the UA know which private key is associated with a certificate it gets back after
   the server has taken the public key created by <keygen> and turned it into a client cert? -->
@@ -104587,6 +104589,7 @@
   Henri Sivonen,
   Henrik Lied,
   Henry Mason,
+  Henry Story,
   Hugh Guiney,
   Hugh Winkler,
   Ian Bicking,

Modified: source
===================================================================
--- source	2014-04-01 18:58:23 UTC (rev 8559)
+++ source	2014-04-02 00:05:19 UTC (rev 8560)
@@ -50791,7 +50791,10 @@
   It is expected that after receiving the <code>SignedPublicKeyAndChallenge</code> (SPKAC)
   structure, the server will generate a client certificate and offer it back to the user for
   download; this certificate, once downloaded and stored in the key store along with the private
-  key, can then be used to authenticate to services that use TLS and certificate authentication.</p>
+  key, can then be used to authenticate to services that use TLS and certificate authentication. For
+  more information, see e.g. <a
+  href="https://wiki.mozilla.org/CA:Certificate_Download_Specification">this MDN article</a>.</p>
+  <!-- or maybe https://developer.mozilla.org/en-US/docs/NSS_Certificate_Download_Specification ? -->
 
   <!-- how does the UA know which private key is associated with a certificate it gets back after
   the server has taken the public key created by <keygen> and turned it into a client cert? -->
@@ -116837,6 +116840,7 @@
   Henri Sivonen,
   Henrik Lied,
   Henry Mason,
+  Henry Story,
   Hugh Guiney,
   Hugh Winkler,
   Ian Bicking,