Giters

spolu / breach_core

A Browser written in JS. Free. Modular. Hackable.

Home Page:https://breach.github.io/breach_core/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not opening, Ubuntu

PhilAndrew opened this issue · comments

commented

[23861:23861:0103/115723:28671887447:FATAL:browser_main_loop.cc(172)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
./breach: line 6: 23861 Aborted (core dumped) $SRC_DIR/AUTO_UPDATE_BUNDLE/exo_browser/exo_browser --raw $SRC_DIR/AUTO_UPDATE_BUNDLE/breach_core
home@home:~/software/breach-v0.3.22-alpha.6-linux-x64$

commented

@PhilAndrew Use one of the chrome sandboxes.

sudo find / -name "*sandbox"

Example:

/usr/lib/chromium-browser/chrome-sandbox
/opt/google/chrome/chrome-sandbox
/opt/google/chrome-beta/chrome-sandbox
/opt/google/chrome-unstable/chrome-sandbox

Then Export:

export CHROME_DEVEL_SANDBOX="_location of chrome sandbox_"

Example:

export CHROME_DEVEL_SANDBOX=/usr/lib/chromium-browser/chrome-sandbox
commented

I've setup my chrome-sandbox and breach still refuses to run:

export CHROME_DEVEL_SANDBOX=/opt/google/chrome-unstable/chrome-sandbox                                                                                                                                                 
 ~  apps  breach  $ ./breach 
[10423:10423:0129/195318:102360922880:FATAL:zygote_host_impl_linux.cc(201)] Check failed: pid_ > 0. Did not find zygote process (using sandbox binary /opt/google/chrome-unstable/chrome-sandbox)
./breach: line 6: 10423 Aborted                 $SRC_DIR/__AUTO_UPDATE_BUNDLE__/exo_browser/exo_browser --raw $SRC_DIR/__AUTO_UPDATE_BUNDLE__/breach_core

I'm running Alpha 0.3.

commented

@captn3m0

Have you tried disabling the Sandbox feature entirely?

sudo rm -rf $(dirname $0)/__AUTO_UPDATE_BUNDLE__/exo_browser/shell/*;
sudo cp -a $(dirname $0)/__AUTO_UPDATE_BUNDLE__/breach_core/* $(dirname $0)/__AUTO_UPDATE_BUNDLE__/exo_browser/shell;
sudo ln -s breach /usr/local/sbin/breach

If using $(dirname $0) does not work, then replace it with the location of you breach folder.
For example my breach folder is breach-v0.3.22-alpha.6-linux-x64, so the commands would look like this for me:

sudo rm -rf breach-v0.3.22-alpha.6-linux-x64/__AUTO_UPDATE_BUNDLE__/exo_browser/shell/*;
sudo cp -a breach-v0.3.22-alpha.6-linux-x64/__AUTO_UPDATE_BUNDLE__/breach_core/* breach-v0.3.22-alpha.6-linux-x64/__AUTO_UPDATE_BUNDLE__/exo_browser/shell;
sudo ln -s breach /usr/local/sbin/breach

then overwrite your breach file with this

#!/usr/bin/env bash

$(dirname $0)/__AUTO_UPDATE_BUNDLE__/exo_browser/exo_browser --disable-setuid-sandbox;

again $(dirname $0) is your breach folder's location, e.g.:

#!/usr/bin/env bash

./breach-v0.3.22-alpha.6-linux-x64/__AUTO_UPDATE_BUNDLE__/exo_browser/exo_browser --disable-setuid-sandbox
commented

I haven't tried disabling the sandbox, but since the method seems complex, and seeing as how I can get chromium raw binaries to work using sandbox, I think it would be better if there was a way to get sandbox working.