Skip to content

Commit

Permalink
[e] (0) Some security notes on the SQL storage APIs.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@1015 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Aug 21, 2007
1 parent 8d99dbb commit 2ed86eb
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 0 deletions.
11 changes: 11 additions & 0 deletions index
Expand Up @@ -28876,6 +28876,17 @@ interface <dfn id=storageitem>StorageItem</dfn> {

<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>
Expand Down
12 changes: 12 additions & 0 deletions source
Expand Up @@ -26386,6 +26386,18 @@ interface <dfn>StorageItem</dfn> {

<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>
Expand Down

0 comments on commit 2ed86eb

Please sign in to comment.