[tahoe-lafs-trac-stream] [tahoe-lafs] #1797: WUI: view content in an HTML5 sandboxed iframe

[tahoe-lafs]

#1797: WUI: view content in an HTML5 sandboxed iframe
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  soon
     Priority:  major    |    Version:  1.9.2
    Component:  code-    |   Keywords:  wui security usability javascript
  frontend-web           |  sandbox same-origin
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Grr, Chrome lost my comment. Will try to reconstruct:

 Which permissions can we allow on an [http://www.whatwg.org/specs/web-apps
 /current-work/multipage/the-iframe-element.html#the-iframe-element iframe
 sandbox attribute]?

 {{{allow-same-origin}}}:
  * No, that would defeat the purpose of sandboxing for us.

 {{{allow-top-navigation}}}:
 {{{allow-popups}}}:
  * No, the navigated frame or popup would be outside the sandbox. The
 sandbox mechanism does not prevent an attacker from navigating directly to
 the unsandboxed content from their own site, but we want to prevent this
 from happening accidentally.

 {{{allow-scripts}}}:
  * Probably OK. We don't care if the sandboxed content can run scripts as
 long as they're in a unique origin. OTOH, this does potentially increase
 the attack surface for browser bugs.

 {{{allow-forms}}}:
  * Probably OK, but it's not clear to me what security property this is
 enforcing at all (since forms can in any case be submitted cross-origin).

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1797#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage