[html5] r6169 - [e] (0) Don't overpromise in security sections... Fixing http://www.w3.org/Bugs/ [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jun 1 10:43:12 PDT 2011
Author: ianh
Date: 2011-06-01 10:43:11 -0700 (Wed, 01 Jun 2011)
New Revision: 6169
Modified:
complete.html
source
Log:
[e] (0) Don't overpromise in security sections...
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12272
Modified: complete.html
===================================================================
--- complete.html 2011-06-01 17:40:37 UTC (rev 6168)
+++ complete.html 2011-06-01 17:43:11 UTC (rev 6169)
@@ -80909,8 +80909,9 @@
<p>Because of the potential for DNS spoofing attacks, one cannot
guarantee that a host claiming to be in a certain domain really is
from that domain. To mitigate this, pages can use TLS. Pages using
- TLS can be sure that only pages using TLS that have certificates
- identifying them as being from the same domain can access their
+ TLS can be sure that only the user, software working on behalf of
+ the user, and other pages using TLS that have certificates
+ identifying them as being from the same domain, can access their
storage areas.</p>
Modified: source
===================================================================
--- source 2011-06-01 17:40:37 UTC (rev 6168)
+++ source 2011-06-01 17:43:11 UTC (rev 6169)
@@ -91920,8 +91920,9 @@
<p>Because of the potential for DNS spoofing attacks, one cannot
guarantee that a host claiming to be in a certain domain really is
from that domain. To mitigate this, pages can use TLS. Pages using
- TLS can be sure that only pages using TLS that have certificates
- identifying them as being from the same domain can access their
+ TLS can be sure that only the user, software working on behalf of
+ the user, and other pages using TLS that have certificates
+ identifying them as being from the same domain, can access their
storage areas.</p>
More information about the Commit-Watchers
mailing list