Changes between Version 1 and Version 2 of Ticket #16010, comment 47


Ignore:
Timestamp:
Aug 12, 2017, 1:48:27 PM (14 months ago)
Author:
gk
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16010, comment 47

    v1 v2  
    44> Level 0 means it is disabled.
    55
    6 Yes, content sandboxing is disabled since Firefox 49 that way (even though https://wiki.mozilla.org/Security/Sandbox is currently suggesting otherwise and I found that out later). What I meant was to test whether it runs with the big patch applied and the configure switch removed that disabled the sandbox explicitly (and with the things enabled which the wiki page claimed to be on level 0). But it seems it does, good.
     6Yes, content sandboxing is disabled since Firefox 49 that way (even though https://wiki.mozilla.org/Security/Sandbox is currently suggesting otherwise and I found that out later). What I meant was to test whether it runs with the big patch applied and the configure switch removed that disabled the sandbox explicitly (and, so I assumed, with the things enabled which the wiki page claimed to be on level 0). But it seems it does, good.
    77
    88> And at Level 1 it can't even start:
     
    1010> NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIScriptSecurityManager.getLoadContextCodebasePrincipal]  remote-browser.xml:376
    1111> TypeError: frameLoader.tabParent is null[Learn More]  remote-browser.xml:256:13
    12 > NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]  remote-browser.xml:44
     12> NS_ERROR_NOT_INITI ALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]  remote-browser.xml:44
    1313> }}}
    1414