search

jseidl / Multi-TOR

Shellscript opens multiple TOR instances
108 stars 43 forks source link

Not connecting - RunAsDaemon is not compatible with relative paths. #6

Closed filebe777 closed 5 years ago

filebe777 commented 5 years ago

root@kali:~/Desktop/Multi-TOR# ./multi-tor.sh 5 Running: tor --RunAsDaemon 1 --CookieAuthentication 0 --HashedControlPassword "" --ControlPort 15001 --PidFile tor1.pid --SocksPort 9051 --DataDirectory data/tor1 Apr 09 05:48:57.036 [notice] Tor 0.3.5.8 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1b, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8. Apr 09 05:48:57.036 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Apr 09 05:48:57.036 [notice] Read configuration file "/etc/tor/torrc". Apr 09 05:48:57.045 [warn] Skipping obsolete configuration option 'WarnUnsafeSocks' Apr 09 05:48:57.045 [warn] Skipping obsolete configuration option 'AllowDotExit' Apr 09 05:48:57.045 [warn] Linelist option '__HashedControlSessionPassword' has no value. Skipping. Apr 09 05:48:57.045 [warn] Path for DataDirectory (data/tor1) is relative and will resolve to /root/Desktop/Multi-TOR/data/tor1. Is this what you wanted? Apr 09 05:48:57.046 [warn] Path for PidFile (tor1.pid) is relative and will resolve to /root/Desktop/Multi-TOR/tor1.pid. Is this what you wanted? Apr 09 05:48:57.046 [warn] Failed to parse/validate config: You have specified at least one relative path (see above) with the RunAsDaemon option. RunAsDaemon is not compatible with relative paths. Apr 09 05:48:57.095 [err] Reading config failed--see warnings above. root@kali:

theraisin commented 5 years ago

You didn't use the up address of your device

On Tue, Apr 9, 2019, 6:54 AM filebe777 notifications@github.com wrote:

root@kali:~/Desktop/Multi-TOR# ./multi-tor.sh 5 Running: tor --RunAsDaemon 1 --CookieAuthentication 0 --HashedControlPassword "" --ControlPort 15001 --PidFile tor1.pid --SocksPort 9051 --DataDirectory data/tor1 Apr 09 05:48:57.036 [notice] Tor 0.3.5.8 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1b, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8. Apr 09 05:48:57.036 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Apr 09 05:48:57.036 [notice] Read configuration file "/etc/tor/torrc". Apr 09 05:48:57.045 [warn] Skipping obsolete configuration option 'WarnUnsafeSocks' Apr 09 05:48:57.045 [warn] Skipping obsolete configuration option 'AllowDotExit' Apr 09 05:48:57.045 [warn] Linelist option '__HashedControlSessionPassword' has no value. Skipping. Apr 09 05:48:57.045 [warn] Path for DataDirectory (data/tor1) is relative and will resolve to /root/Desktop/Multi-TOR/data/tor1. Is this what you wanted? Apr 09 05:48:57.046 [warn] Path for PidFile (tor1.pid) is relative and will resolve to /root/Desktop/Multi-TOR/tor1.pid. Is this what you wanted? Apr 09 05:48:57.046 [warn] Failed to parse/validate config: You have specified at least one relative path (see above) with the RunAsDaemon option. RunAsDaemon is not compatible with relative paths. Apr 09 05:48:57.095 [err] Reading config failed--see warnings above. root@kali:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jseidl/Multi-TOR/issues/6, or mute the thread https://github.com/notifications/unsubscribe-auth/APxA8YfPx4S_rn2anmnctt1A1Q0mwqwwks5vfJuQgaJpZM4ckj7Q .

jseidl commented 5 years ago

Yeah it expects you to give a full absolute path in order to avoid vulnerabilities that come from relative paths.

nullitall commented 3 years ago

heres a fix https://github.com/nullitall/multitor