Enhacement: add tor+i2p direct access

[nyancat18]

You could add i2p and tor direct accesses with adding some lines to the pkgbuild such as these https://gist.github.com/triceratops1/d1dc789d44a607e2d0902d2f0040b94a

what does these lines?

Create 2 desktop files (inox-i2p, inox-tor) Makes these desktop files open inox with tor or i2p (with counter dns-leak countermeasures)

[gcarq]

I like your engagement, but it is NOT recommended to run inox with tor or i2p, because there is a high possibility of unseen tracking features in the code and with each update.

You can create a PR for README.md which describes how to use a proxy, but i will not create additional shortcuts or encourage anyone to use inox with tor.

[nyancat18]

OK for inox torified: inox --proxy-server="socks5://localhost:9050" --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost"

explanation: https://www.chromium.org/developers/design-documents/network-stack/socks-proxy

The flag host-resolver-rules, forces inox to use the tor's DNS The flag EXCLUDE, lets inox resolve the proxy http://tor.stackexchange.com/questions/3435/how-do-i-configure-chrome-to-use-tor

For I2P https://www.internalpointers.com/post/run-chrome-chromium-proxy-settings-linux

inox --proxy-server="http://127.0.0.1:4444" doen't need host-resolver*rules and EXCLUDE, because i2p its a closed networs (the dns is throught i2p, no clearnet)

WARNING: IFYOU'VE A PROXY EXTENSION INSTALLED, THE --proxy-server options DOESN'T WORK

AT GIST https://gist.github.com/triceratops1/952b1acd38c480de3f8f71d9fdb57346

[gcarq]

Thanks. Added to README

[nyancat18]

@gcarq Could you add the warning:

If you have a proxy extension, this config couldn't work?

[nyancat18]

pd could you merge #46 with this issue?

its a readme enhacement too (a sandbox, nice if you trorify/i2pify)+memory saving (double sandbox, the inox's hardened+firejail )

[gcarq]

I will look into it ASAP.

Closed. Duplicate of https://github.com/gcarq/inox-patchset/issues/46