- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 05 Mar 2012 18:58:56 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv27969
Modified Files:
Overview.html iana.html spec.html spec.preprocessed.html
Log Message:
http+aes: Clarify that the nonce is zero and that thus the key must be fresh with each resource. (whatwg r7014)
[updated by splitter]
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.1750
retrieving revision 1.1751
diff -u -d -r1.1750 -r1.1751
--- Overview.html 5 Mar 2012 05:58:48 -0000 1.1750
+++ Overview.html 5 Mar 2012 18:58:43 -0000 1.1751
@@ -364,7 +364,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5603.</p>
+ This is revision 1.5604.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.1893
retrieving revision 1.1894
diff -u -d -r1.1893 -r1.1894
--- spec.html 5 Mar 2012 05:58:48 -0000 1.1893
+++ spec.html 5 Mar 2012 18:58:44 -0000 1.1894
@@ -365,7 +365,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5603.</p>
+ This is revision 1.5604.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -28475,12 +28475,12 @@
<dd>Same as <code title="">http</code>, except that the message
body must be decrypted by applying the AES-CTR algorithm using the
key specified in the URL's <code title="">userinfo</code>
- component, after unescaping it from the URL syntax to bytes. If
- there is no such component, or if that component, when unescaped
- from the URL syntax to bytes, does not consist of exactly 16, 24,
- or 32 bytes, then the user agent must act as if the resource could
- not be obtained due to a network error, and may report the problem
- to the user.</dd>
+ component, after unescaping it from the URL syntax to bytes, and
+ using a zero nonce. If there is no such component, or if that
+ component, when unescaped from the URL syntax to bytes, does not
+ consist of exactly 16, 24, or 32 bytes, then the user agent must
+ act as if the resource could not be obtained due to a network
+ error, and may report the problem to the user.</dd>
<dt>Encoding considerations:</dt>
<dd>Same as <code title="">http</code>, but the <code title="">userinfo</code> component represents bytes encoded using
ASCII and the URL escape mechanism.</dd>
@@ -28526,6 +28526,10 @@
categorised by an attacker watching network traffic or with access
to the system hosting the files without the attacker ever having
to decrypt the "data.json" files.</p>
+ <p>Each resource encrypted in this fashion must use a fresh key.
+ Otherwise, an attacker can use commonalities in the resources'
+ plaintexts to determine the key and decrypt all the resources
+ sharing a key.</p>
<p>The security considerations that apply to <code title="">http</code> apply as well.</p>
</dd>
Index: spec.preprocessed.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.preprocessed.html,v
retrieving revision 1.732
retrieving revision 1.733
diff -u -d -r1.732 -r1.733
--- spec.preprocessed.html 5 Mar 2012 05:58:58 -0000 1.732
+++ spec.preprocessed.html 5 Mar 2012 18:58:53 -0000 1.733
@@ -381,7 +381,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5603.</p>
+ This is revision 1.5604.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -28365,12 +28365,12 @@
<dd>Same as <code title="">http</code>, except that the message
body must be decrypted by applying the AES-CTR algorithm using the
key specified in the URL's <code title="">userinfo</code>
- component, after unescaping it from the URL syntax to bytes. If
- there is no such component, or if that component, when unescaped
- from the URL syntax to bytes, does not consist of exactly 16, 24,
- or 32 bytes, then the user agent must act as if the resource could
- not be obtained due to a network error, and may report the problem
- to the user.</dd>
+ component, after unescaping it from the URL syntax to bytes, and
+ using a zero nonce. If there is no such component, or if that
+ component, when unescaped from the URL syntax to bytes, does not
+ consist of exactly 16, 24, or 32 bytes, then the user agent must
+ act as if the resource could not be obtained due to a network
+ error, and may report the problem to the user.</dd>
<dt>Encoding considerations:</dt>
<dd>Same as <code title="">http</code>, but the <code title="">userinfo</code> component represents bytes encoded using
ASCII and the URL escape mechanism.</dd>
@@ -28416,6 +28416,10 @@
categorised by an attacker watching network traffic or with access
to the system hosting the files without the attacker ever having
to decrypt the "data.json" files.</p>
+ <p>Each resource encrypted in this fashion must use a fresh key.
+ Otherwise, an attacker can use commonalities in the resources'
+ plaintexts to determine the key and decrypt all the resources
+ sharing a key.</p>
<p>The security considerations that apply to <code title="">http</code> apply as well.</p>
</dd>
Index: iana.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/iana.html,v
retrieving revision 1.606
retrieving revision 1.607
diff -u -d -r1.606 -r1.607
--- iana.html 2 Mar 2012 23:58:29 -0000 1.606
+++ iana.html 5 Mar 2012 18:58:44 -0000 1.607
@@ -704,12 +704,12 @@
<dd>Same as <code title="">http</code>, except that the message
body must be decrypted by applying the AES-CTR algorithm using the
key specified in the URL's <code title="">userinfo</code>
- component, after unescaping it from the URL syntax to bytes. If
- there is no such component, or if that component, when unescaped
- from the URL syntax to bytes, does not consist of exactly 16, 24,
- or 32 bytes, then the user agent must act as if the resource could
- not be obtained due to a network error, and may report the problem
- to the user.</dd>
+ component, after unescaping it from the URL syntax to bytes, and
+ using a zero nonce. If there is no such component, or if that
+ component, when unescaped from the URL syntax to bytes, does not
+ consist of exactly 16, 24, or 32 bytes, then the user agent must
+ act as if the resource could not be obtained due to a network
+ error, and may report the problem to the user.</dd>
<dt>Encoding considerations:</dt>
<dd>Same as <code title="">http</code>, but the <code title="">userinfo</code> component represents bytes encoded using
ASCII and the URL escape mechanism.</dd>
@@ -755,6 +755,10 @@
categorised by an attacker watching network traffic or with access
to the system hosting the files without the attacker ever having
to decrypt the "data.json" files.</p>
+ <p>Each resource encrypted in this fashion must use a fresh key.
+ Otherwise, an attacker can use commonalities in the resources'
+ plaintexts to determine the key and decrypt all the resources
+ sharing a key.</p>
<p>The security considerations that apply to <code title="">http</code> apply as well.</p>
</dd>
Received on Monday, 5 March 2012 18:59:06 UTC