Silk Road forums
Discussion => Security => Topic started by: monrovia on December 20, 2012, 04:08 am
-
K, so I'm not serious about the title, but my patience is running thin. I tried Liberte, I tried Ubuntu, I just tried Tails. I got the OS to boot correctly(just like the last 2 times), but ran into issues with the internet. Again. I'm pretty sure I'm not doing anything wrong because Liberte and Tails seem like they had the EXACT same problem. I'm kind of exited to delve into the Linux world, so it's extremely frustrating to have problems right off the bat.
So I booted Tails from a DVD, it started fine. I place my mouse pointer over 'internet,' and click on the torified browser. A window pops up with this message....."vidalia detected that the Tor software exited unexpectedly. Please check the message log for recent warning or error messages."
I check the message log, and the last 5 entries are as follows....
---------------------------------------------------
Warning: Directory /var/run/tor does not exist
Warning: Before Tor can create a control socket in "/var/run/tor/control," the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (on some unit systems, anybody who can list a socket can connect to it, so Tor is being careful)
Notice: Closing partially-constructed socks listener on 127.0.0.1:9050.
Warning Failed to parse/validate config: Failed to bind one of the listener ports.
Error: Reading config failed--See warnings above.
---------------------------------------------------
When I tried Liberte, I had a similar message telling me to check some sort of logs after I tried opening the torified browser as well. Is there some issue with my hardware that is causing me to have these Linux issues? Can anyone give any suggestions for what I should do? Should I just give up and save a little money for a laptop?(which I'm doing eventually anyway)
Fuck this is aggravating.
-
Have you tried on a different machine? Wired or wireless connection? Study up on linux.
-
Warning: Directory /var/run/tor does not exist
Warning: Before Tor can create a control socket in "/var/run/tor/control," the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (on some unit systems, anybody who can list a socket can connect to it, so Tor is being careful)
Edit: the info that I had here won't be useful, based on what I've learned about Tails, see below.
-
Failed to bind one of the listener ports.
You get this error message when one instance of Tor is already running. If there's a system version of Tor running and you try to launch TBB, which starts its own instance of Tor, you'll get that error.
-
Failed to bind one of the listener ports.
You get this error message when one instance of Tor is already running. If there's a system version of Tor running and you try to launch TBB, which starts its own instance of Tor, you'll get that error.
I tried opening the browser again and didn't realize that Tor was still running, so those last 2 must have been logged after that. Thanks for the help, I'm going to print this stuff out and try it tomorrow hopefully.
-
This is fucking retarded...
Open a terminal (run the "gnome-terminal" or "xterm" commands), and type this exactly:
sudo pkill -f tor
sleep 5
echo 'SocksPort 9050' >> /etc/tor/torrc
sudo tor
... then start the internet browser, and set the proxy port to be 9050. Fuck whatever Tails thinks it's got configured properly -- override it.
-
What the OP hasn't made clear is whether or not they verified that the .iso image for Tails was correct or not.
Ideally, one should verify the Tails .iso image against its' detached PGP signature, as follows:
gpg --verify tails-i386-0.15.iso.pgp tails-i386-0.15.iso
gpg: armor header: Version: GnuPG v1.4.12 (GNU/Linux)
gpg: Signature made Mon 26 Nov 2012 08:45:14 AM EST using RSA key ID BE2CD9C1
gpg: NOTE: signature key BE2CD9C1 expired Sat 06 Oct 2012 05:29:24 AM EDT
gpg: Good signature from "Tails developers (signing key) <tails@boum.org>"
gpg: aka "T(A)ILS developers (signing key) <amnesia@boum.org>"
gpg: WARNING: Using untrusted key!
gpg: binary signature, digest algorithm SHA512
NC