[tor-talk] What is going on with /var/run/tor?
I am becoming increasingly perplexed about my Tor setup. Tor does not appear to run on start-up. I assume this because I cannot see it using ps aux | grep tor. My torrc is in /etc/tor/torrc with user and group set as 'root'. I run 'sudo tor' and receive the following errors: Dec 29 20:12:55.076 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:12:55.079 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:12:55.079 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.079 [warn] Directory /var/run/tor does not exist. Dec 29 20:12:55.079 [warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.) Dec 29 20:12:55.079 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.080 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 20:12:55.080 [err] Reading config failed--see warnings above. It is correct that /var/run/tor does not exist. I then create /var/run/tor with user and group as 'root' and run 'sudo tor' again: Dec 29 20:15:41.943 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:15:41.948 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:15:41.948 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:15:41.949 [warn] /var/run/tor is not owned by this user (debian-tor, 115) but by root (0). Perhaps you are running Tor as the wrong user? Dec 29 20:15:41.949 [warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.) Dec 29 20:15:41.950 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050 Dec 29 20:15:41.950 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 20:15:41.950 [err] Reading config failed--see warnings above. I don't understand why I get this error because I am 'root' not 'debian-tor'. Su-ing into root then running tor provides the same error message: However, running 'tor' (without sudo) provides the following message: Dec 29 20:18:28.270 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:18:28.271 [warn] Could not open /etc/tor/torrc: Permission denied Dec 29 20:18:28.272 [notice] Configuration file /etc/tor/torrc not present, using reasonable defaults. Dec 29 20:18:28.274 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:18:28.274 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:18:28.285 [notice] Parsing GEOIP file /usr/share/tor/geoip. Dec 29 20:18:29.084 [notice] OpenSSL OpenSSL 0.9.8k 25 Mar 2009 [9080bf] looks like it's older than 0.9.8l, but some vendors have backported 0.9.8l's renegotiation code to earlier versions, and some have backported the code from 0.9.8m or 0.9.8n. I'll set both SSL3_FLAGS and SSL_OP just to be safe. Dec 29 20:18:31.459 [notice] We now have enough directory information to build circuits. Dec 29 20:18:31.459 [notice] Bootstrapped 80%: Connecting to the Tor network. Dec 29 20:18:32.522 [notice] Bootstrapped 85%: Finishing handshake with first hop. Dec 29 20:18:33.603 [notice] Bootstrapped 90%: Establishing a Tor circuit. Dec 29 20:18:34.618 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Dec 29 20:18:34.618 [notice] Bootstrapped 100%: Done. This all looks good except that it now uses reasonable defaults rather than my specific torrc file. I also have no idea why running 'tor' doesn't complain about /var/run/tor but running 'sudo tor' does. All I want to do is to run tor and have it load a specific torrc. I don't care whether I run tor in GNOME or whether I load Vidalia which then loads tor. At the moment, Vidalia just gives the /var/run/tor error as above. Suggestions please? Many thanks. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] What is going on with /var/run/tor?
On 2011-12-29 21:25, Matthew R wrote: I am becoming increasingly perplexed about my Tor setup. Tor does not appear to run on start-up. I assume this because I cannot see it using ps aux | grep tor. My torrc is in /etc/tor/torrc with user and group set as 'root'. I run 'sudo tor' and receive the following errors: Dec 29 20:12:55.076 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:12:55.079 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:12:55.079 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.079 [warn] Directory /var/run/tor does not exist. Dec 29 20:12:55.079 [warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.) Dec 29 20:12:55.079 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.080 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 20:12:55.080 [err] Reading config failed--see warnings above. It is correct that /var/run/tor does not exist. I then create /var/run/tor with user and group as 'root' and run 'sudo tor' again: Dec 29 20:15:41.943 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:15:41.948 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:15:41.948 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:15:41.949 [warn] /var/run/tor is not owned by this user (debian-tor, 115) but by root (0). Perhaps you are running Tor as the wrong user? Dec 29 20:15:41.949 [warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.) Dec 29 20:15:41.950 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050 Dec 29 20:15:41.950 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 20:15:41.950 [err] Reading config failed--see warnings above. I don't understand why I get this error because I am 'root' not 'debian-tor'. Su-ing into root then running tor provides the same error message: However, running 'tor' (without sudo) provides the following message: Dec 29 20:18:28.270 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:18:28.271 [warn] Could not open /etc/tor/torrc: Permission denied Dec 29 20:18:28.272 [notice] Configuration file /etc/tor/torrc not present, using reasonable defaults. Dec 29 20:18:28.274 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:18:28.274 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:18:28.285 [notice] Parsing GEOIP file /usr/share/tor/geoip. Dec 29 20:18:29.084 [notice] OpenSSL OpenSSL 0.9.8k 25 Mar 2009 [9080bf] looks like it's older than 0.9.8l, but some vendors have backported 0.9.8l's renegotiation code to earlier versions, and some have backported the code from 0.9.8m or 0.9.8n. I'll set both SSL3_FLAGS and SSL_OP just to be safe. Dec 29 20:18:31.459 [notice] We now have enough directory information to build circuits. Dec 29 20:18:31.459 [notice] Bootstrapped 80%: Connecting to the Tor network. Dec 29 20:18:32.522 [notice] Bootstrapped 85%: Finishing handshake with first hop. Dec 29 20:18:33.603 [notice] Bootstrapped 90%: Establishing a Tor circuit. Dec 29 20:18:34.618 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Dec 29 20:18:34.618 [notice] Bootstrapped 100%: Done. This all looks good except that it now uses reasonable defaults rather than my specific torrc file. I also have no idea why running 'tor' doesn't complain about /var/run/tor but running 'sudo tor' does. All I want to do is to run tor and have it load a specific torrc. I don't care whether I run tor in GNOME or whether I load Vidalia which then loads tor. At the moment, Vidalia just gives the /var/run/tor error as above. Suggestions please? Many thanks. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk Why would you like to run tor as root? U mad bro? Do the following: chown debian-tor:debian-tor /var/run/tor Now tor shouldn't complain 'bout the wrong usergroup anymore. greetz
Re: [tor-talk] What is going on with /var/run/tor?
On Thu, Dec 29, 2011 at 08:25:14PM +, magick...@gmail.com wrote 4.6K bytes in 98 lines about: : Tor does not appear to run on start-up. I assume this because I cannot see : it using ps aux | grep tor. What did you install? It sounds like you may have two tor installations. Or at least, two tor configs that cause tor to be configured in two very different ways. -- Andrew http://tpo.is/contact pgp 0x74ED336B ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Automatic vulnerability scanning of Tor Network?
Hello Gozu, On Wed, 28 Dec 2011, Gozu-san wrote: On 28/12/11 03:42, John Case wrote: Don't run Tor from an IP with your name attached to it. Anonymous server rental is nontrivial. What degree of non-attachment is sufficient, in your opinion? I disagree. Once you move past the big cloud players, you get into a morass of small, cutthroat VPS providers who are all barely surviving on thin margins. Without question you can find one that will respond very nicely to an official RFQ and a money order. If you buy the MO from an actual bank, it will look very much like a cashiers check, etc. Alternatively, a pre-paid visa from somewhere like Simon malls, etc., works well. The real hook is a single, annual payment, which will be impossible for them to resist. That's one end of the spectrum... The other end of the spectrum is a corporate front with an appointed agent, etc. - you can do this for less than $500, and then you can run everything under that. Either way your name is not attached to it, and your home address, etc., isn't either. The list may not appreciate my criticism, but the reality is we get about one post every six months from someone who literally has their door kicked in and their property stolen by the state. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] If you have access to certain tools, you can completely ignore Tor.
- Original Message - From: Joe Btfsplk Sent: 12/26/11 12:57 AM To: tor-talk@lists.torproject.org Subject: Re: [tor-talk] If you have access to certain tools, you can completely ignore Tor. On 12/24/2011 4:09 AM, grarpamp wrote: to put one in someday, we'll make it obvious and loud that it is so. No Backdoors. No bugdoors. No so-called lawful interception systems. Court orders and duress can be applied to anyone who is reachable by them. The only real solution should that happen is to take things underground on Tor, or any other strong net, and remain open source therein. It is unfortunate in this regard that the current systems employ known authors. But new unknowns will step in place of the old if need be. Good point. I think you're right. They may have to go WAY underground. Everyone knows several countries have already outlawed Tor other internet uses / sites. Julian Assange was way to visible to carry out his mission, whether one agrees w/ his agenda or not. If gov'ts can't stop persons / organizations they deem embarrassing or threats because of free speech rights, they'll invent other charges against them. Again, I just can't see many gov'ts leaving Tor alone, when (unfortunately) it * presumably *allows combatant enemies to easily communicate anonymously. Democratic nations may not ban it, but they have to protect their national security they won't sit idly by while terrorist groups thumb their noses at security agencies. It's unfortunate that the use of Tor for true, non-violent free speech access to info it's use for more sinister purposes get mixed together. It was once unthinkable that US other free countries would listen in on potentially all citizens' conversations or read private mail (electronic or paper) w/o court warrants, but it's here so far, people pretty much accept it. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk Could you possibly supply a list of truly democratic countries? I don't think anymore exist - in reality. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] What is going on with /var/run/tor?
On 2011-12-29, Matthew R magick...@gmail.com wrote: I am becoming increasingly perplexed about my Tor setup. Tor does not appear to run on start-up. I assume this because I cannot see it using ps aux | grep tor. My torrc is in /etc/tor/torrc with user and group set as 'root'. I run 'sudo tor' and receive the following errors: Dec 29 20:12:55.076 [notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Dec 29 20:12:55.079 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Dec 29 20:12:55.079 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.079 [warn] Directory /var/run/tor does not exist. Dec 29 20:12:55.079 [warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.) Dec 29 20:12:55.079 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050 Dec 29 20:12:55.080 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Dec 29 20:12:55.080 [err] Reading config failed--see warnings above. It is correct that /var/run/tor does not exist. I then create /var/run/tor with user and group as 'root' and run 'sudo tor' again: [snipped] I don't understand why I get this error because I am 'root' not 'debian-tor'. Su-ing into root then running tor provides the same error message: See /usr/share/doc/tor/README.Debian . /var/run/tor needs to be owned by the debian-tor user and group. Robert Ransom ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Differences between real exit traffic and exit-generated traffic ?
On 2011-12-30, John Case c...@sdf.org wrote: Let's say I have an exit node handling average traffic and number of connections (whatever that is). Let's also say that port 22 is included in my exit policy. Now let's say that I, as the administrator, log onto the exit node and: ssh u...@host.com I understand that a global observer with traffic analysis blah blah blah. But what about someone just watching the exit node ? Is there anything at all about my ssh connection generate from within the exit node that would distinguish it from real exiting Tor traffic ? Someone watching all traffic to and from the exit node would be able to distinguish that connection from Tor traffic because traffic on the SSH connection would not be relayed over any OR connection (in either direction). Someone watching only that SSH connection (e.g. a sniffer at host.com) would be able to distinguish that SSH connection from an exiting Tor stream because your SSH client would respond to messages from the server immediately after they reach the exit node, whereas an SSH client connecting over Tor would not be able to respond until data from the server reached the other end of a Tor circuit. Robert Ransom ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
