WSA, Exploitshield, SBIE conflict

Discussion in 'Prevx Releases' started by ParaNodes, Mar 31, 2013.

Thread Status:
Not open for further replies.
  1. ParaNodes

    ParaNodes Registered Member

    Joined:
    Jul 15, 2003
    Posts:
    69
    Testing the new ES 0.9.1 beta, came across this interesting conflict.
    WSA and ES play nice as long as SBIE isn't thrown in the mix.
    Using latest WSA, ES 0.9.1 beta, SBIE 3.76 opening firefox default sbie box shows nothing on monitor(i.e.does not render FF onto monitor), all sbie and FF processes are looking normal from process explorer(except ES.dll is blocked) , sbie window shows all processes normal except FF icon shows a folder icon instead, shut down protection WSA solves issue( tried disabling all shields one at a time, no luck), like wise with ES not installed everything is normal.

    Just a heads up for anyone interested.
    Edit: To add ,tested on W7pro x64
     
    Last edited: Mar 31, 2013
  2. Umbra

    Umbra Registered Member

    Joined:
    Feb 10, 2011
    Posts:
    2,211
    Location:
    in a remote land :)
    the latest Sbie v4 beta works bad with WSA's browser protection (in ID shield), it block much of WSA hooks , so you have to set the Browser on "Allowed" only and not "Protected"
     
  3. shadek

    shadek Registered Member

    Joined:
    Feb 26, 2008
    Posts:
    2,363
    Location:
    Sweden
    Yes. Sandboxie functions in a way that blocks communication outside of the sandbox (which is the whole purpose of Sandboxie). Therefore the sandboxed browser must be "allowed" instead of "protected" in WSA.
     
Thread Status:
Not open for further replies.