SusmithKrishnan / torghost

TorGhost is an anonymization script. TorGhost redirects all internet traffic through SOCKS5 tor proxy. DNS requests are also redirected via tor, thus preventing DNSLeak. The scripts also disables unsafe packets exiting the system. Some packets like ping request can compromise your identity.
GNU General Public License v3.0
848 stars 280 forks source link

Connect torghost via bridge #49

Open johnmcaphy opened 4 years ago

johnmcaphy commented 4 years ago

tor is censored in my country.

how can i force torghost use BridgeDB IPs?

or enter manually the bridge IP that i know.

SusmithKrishnan commented 4 years ago

Torghost uses '/etc/tor/torghostrc' config file to run tor daemon. You can edit this file as you would edit a 'torrc' file.

To use Bridges you need to add few lines in 'torghostrc' file

 UseBridges 1
 Bridge obfs4 <ip:port> <key>

example:

 UseBridges 1
 Bridge obfs4 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413

You can add multiple bridges by appending the address and key.

johnmcaphy commented 4 years ago

i tried and nothing! i can connect with tor browser with bridge that i added to torghostrc file but torghost can't (so the issus isn't from bridge): my torghostrc

` VirtualAddrNetwork 10.0.0.0/10 AutomapHostsOnResolve 1 TransPort 9040 DNSPort 5353 ControlPort 9051 RunAsDaemon 1 UseBridges 1 Bridge obfs4 82.255.154.217:34161 29C8E90E8FEBB7F5F67C4364224FBF4747DFA0A6 Bridge obfs4 2.56.213.50:80 33BC98A26B0DAA480C3CFE1A4EA50A29154DFB4B Bridge obfs4 185.183.96.124:25476 BB830E902C543786120C76D9D07A6A7C767338CA

`

johnmcaphy commented 4 years ago

UPDATE: i monitor my traffic with wireshark and realized torghost try to connect to bridges ip that i writed in torghostrc. so it's not torghost issue.

can anyone guess what's wrong and help me?! (Tor is censored in my country)

SusmithKrishnan commented 4 years ago

Try different protocols like obfs3, scramblesuit see if it works. Also, post the output of sudo -u debian-tor tor -f /etc/tor/torghostrc

johnmcaphy commented 4 years ago

before start torghost: Dec 29 15:07:30.336 [notice] Tor 0.4.2.5 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.4. Dec 29 15:07:30.336 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 29 15:07:30.337 [notice] Read configuration file "/etc/tor/torghostrc". Dec 29 15:07:30.338 [warn] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible. Dec 29 15:07:30.341 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 15:07:30.341 [notice] Opened Socks listener on 127.0.0.1:9050 Dec 29 15:07:30.341 [notice] Opening DNS listener on 127.0.0.1:5353 Dec 29 15:07:30.341 [notice] Opened DNS listener on 127.0.0.1:5353 Dec 29 15:07:30.341 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 Dec 29 15:07:30.341 [notice] Opened Transparent pf/netfilter listener on 127.0.0.1:9040 Dec 29 15:07:30.341 [notice] Opening Control listener on 127.0.0.1:9051 Dec 29 15:07:30.341 [notice] Opened Control listener on 127.0.0.1:9051

after Dec 29 15:08:02.033 [notice] Tor 0.4.2.5 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.4. Dec 29 15:08:02.033 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 29 15:08:02.033 [notice] Read configuration file "/etc/tor/torghostrc". Dec 29 15:08:02.034 [warn] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible. Dec 29 15:08:02.037 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 15:08:02.037 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running? Dec 29 15:08:02.038 [notice] Opening DNS listener on 127.0.0.1:5353 Dec 29 15:08:02.038 [notice] Opened DNS listener on 127.0.0.1:5353 Dec 29 15:08:02.038 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 Dec 29 15:08:02.038 [warn] Could not bind to 127.0.0.1:9040: Address already in use. Is Tor already running? Dec 29 15:08:02.038 [notice] Opening Control listener on 127.0.0.1:9051 Dec 29 15:08:02.038 [warn] Could not bind to 127.0.0.1:9051: Address already in use. Is Tor already running? Dec 29 15:08:02.038 [notice] Closing partially-constructed DNS listener on 127.0.0.1:5353 Dec 29 15:08:02.038 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 15:08:02.038 [err] Reading config failed--see warnings above.