[Webkit-unassigned] [Bug 64079] Sandboxed iframe gives misleading xss-error

[bugzilla-daemon at webkit.org]

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


Mike West <mkwst at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
           Keywords|                            |WebExposed
           Priority|P2                          |P3
         AssignedTo|webkit-unassigned at lists.web |mkwst at chromium.org
                   |kit.org                     |
                 CC|                            |mkwst at chromium.org
     Ever Confirmed|0                           |1




--- Comment #2 from Mike West <mkwst at chromium.org>  2012-09-09 11:43:02 PST ---
Hey, logging improvements!

I've taken a quick stab at this. There's a FIXME comment suggesting that the error message generation might be better pushed out to SecurityOrigin; I started in that direction, but I backed out after reading some other comments.

Specifically, moving the generation of this error message into SecurityOrigin means that we won't be able to check the sandbox flags directly on the SecurityContext/Documents in question. We'd just be looking at SecurityOrigin::isUnique. Would that be enough? There's a comment on that method noting subtle differences between a sandboxed frame and a frame with a unique origin. WDYT, Adam?

I'll upload a patch in a moment with a trivial approach, but if moving it to SecurityOrigin is the better option, I'm happy to go in that direction.

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