[html5] r1015 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-08-21 00:37:43 -0700 (Tue, 21 Aug 2007)
New Revision: 1015

Modified:
   index
   source
Log:
[e] (0) Some security notes on the SQL storage APIs.

Modified: index
===================================================================
--- index	2007-08-21 00:25:51 UTC (rev 1014)
+++ index	2007-08-21 07:37:43 UTC (rev 1015)
@@ -28876,6 +28876,17 @@
 
   <h4 id=executing><span class=secno>4.12.2. </span>Executing SQL statements</h4>
 
+  <p class=big-issue>There are two major missing features here: One: a way to
+   be secure against DNS spoofing (a database created over an SSL connection
+   covered by one cert should not be made accessible to content connecting
+   with another cert or with no cert). Two: there's no session-specific API,
+   so if you have two windows open at once, you can't interact with the site
+   doing two separate sessions unless the site goes out of its way to track
+   sessions itself, detecting when new tabs are opened, etc. sessionStorage[]
+   handles it, why doesn't this? Also, we need to be more explicit about disk
+   usage concerns, quota, etc. Some of the security notes from
+   globalStorage[] should maybe come down here.
+
   <p>Each <a href="#origin0">origin</a> must have an associated database
    unique to that origin. An author can interact with the database using the
    <code title=dom-executeSql><a href="#executesql">executeSql()</a></code>

Modified: source
===================================================================
--- source	2007-08-21 00:25:51 UTC (rev 1014)
+++ source	2007-08-21 07:37:43 UTC (rev 1015)
@@ -26386,6 +26386,18 @@
 
   <h4>Executing SQL statements</h4>
 
+  <p class="big-issue">There are two major missing features here: One:
+  a way to be secure against DNS spoofing (a database created over an
+  SSL connection covered by one cert should not be made accessible to
+  content connecting with another cert or with no cert). Two: there's
+  no session-specific API, so if you have two windows open at once,
+  you can't interact with the site doing two separate sessions unless
+  the site goes out of its way to track sessions itself, detecting
+  when new tabs are opened, etc. sessionStorage[] handles it, why
+  doesn't this? Also, we need to be more explicit about disk usage
+  concerns, quota, etc. Some of the security notes from
+  globalStorage[] should maybe come down here.</p>
+
   <p>Each <span>origin</span> must have an associated database unique
   to that origin. An author can interact with the database using the
   <code title="dom-executeSql">executeSql()</code> method.</p>