[Webkit-unassigned] [Bug 21288] Implement HTML5's sandbox attribute for iframes

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=21288





--- Comment #43 from Darin Adler <darin at apple.com>  2009-11-18 09:19:09 PST ---
(In reply to comment #42)
> W.r.t. the equal() issue: The way a sandboxed origin is modeled in HTML5 is as
> a "unique value," which you can think of as a random string for each instance
> that's not equal to anything except itself.  We might improve our
> implementation of sandboxed SecurityOrigins by representing them this way.  If
> we do that, it's clear that two sandboxed origins are equal if, and only if,
> they are the same physical object.

That sounds like a good design. When sandboxed, a SecurityOrigin would not
check anything except object identity to determine equality and to do hashing.

I'm also not sure we want to allow storage and database access from these
sandboxed origins even temporarily. So it is good, but may not be enough to
simply make it compare unequal to all other origins. I suspect that in any case
we will need to add "can" type checks to StorageNamespaceImpl::storageArea and
a some of the functions in DatabaseTracker so that storage and database access
are subject to sandboxing rules.

But I don't know for sure. What behavior do we want for storage and database?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.