- tor-relays - lists.torproject.org

Manual Relay Guide for OS X
by Zachary Alberico 04 Apr '15

04 Apr '15

Hi Tor-Relays, I wrote the following documentation after figuring out how to get my Tor relay working with a manual install. The goal is to give easy to follow and concise instructions that explain just enough to understand what you're doing. I'm trying to find out the best way to make this available - would it be possible to add it to the externally facing documentation? I'd also really appreciate it if someone looks it over and sees if I made any typos/forgot something. I can help with whatever needs to be done. Thanks, Zach ### Manually configuring a Tor Relay on OS X (Yosemite, Tor 0.2.5.11) This guide walks you through the process of configuring your very own tor relay explaining each step along the way. First install homebrew which will allow us to install the most recent version of Tor (http://brew.sh) The following command pasted into a terminal will download and install homebrew. {code} ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" {code} Once that completes we'll use homebrew to install tor with the following command. {code} brew install tor {code} At this point tor should be installed and the homebrew command should have printed the following: {quote} You will find a sample `torrc` file in /usr/local/etc/tor. It is advisable to edit the sample `torrc` to suit your own security needs: https://www.torproject.org/docs/faq#torrc After editing the `torrc` you need to restart tor. To have launchd start tor at login: ln -svn /usr/local/opt/tor/*.plist ~/Library/LaunchAgents Then to load tor now: launchctl load ~/Library/LaunchAgents/homebrew.mxcl.tor.plist {quote} Notice that it mentions the location of the torrc file (we're going to edit that next). It also explains how to have tor run at startup and how to start it now. Before we go ahead and run those commands let's create the location logging is supposed to go since for some reason it doesn't already exist. These commands are creating directories. {code} mkdir /usr/local/Cellar/tor/0.2.5.11/var mkdir /usr/local/Cellar/tor/0.2.5.11/var/log mkdir /usr/local/Cellar/tor/0.2.5.11/var/log/tor {code} Similarly create the following for the DataDirectory if it doesn't already exist. {code} mkdir /usr/local/Cellar/tor/0.2.5.11/var/lib mkdir /usr/local/Cellar/tor/0.2.5.11/var/lib/tor {code} Next let's edit the torrc.sample file and save it as torrc. To open its location in a finder window use the following command: {code} open /usr/local/etc/tor {code} Then open the torrc.sample file in your chosen editor (text edit works fine). Read through the file and try to understand what each of the options are, at a minimum we're going to want to uncomment and use the following options. {code} #Sets the logging location Log notice file /usr/local/Cellar/tor/0.2.5.11/var/log/tor/notices.log #Sets the DataDirectory DataDirectory /usr/local/Cellar/tor/0.2.5.11/var/lib/tor #If you're only configuring this as a relay SocksPort 0 #Your main ORPort ORPort 9001 #Name of your relay Nickname supercoolrelay #Bandwidth limits RelayBandwidthRate 5000 KB RelayBandwidthBurst 10000 KB #Way for the tor project to conact you ContactInfo Random Person <a special email you should make just for this>@gmail.com #What port to advertise for directory connections DirPort 9030 #If you don't want to run an exit (if you're able to run an exit please use the file default!) ExitPolicy reject *:* # no exits allowed {code} Once you've uncommented/edited those lines save the file as torrc and exit. Now it's time for an oversimplified and possibly inaccurate lesson about Networking. You are probably sitting at a home network at a computer connected wirelessly or wired to a router which is connected to a modem which is connecting you to the outside Internet. Your entire network connection has one IPv4 address facing the outside world. Your router then uses NAT which stands for Network Address Translation to remap traffic to the unique IP addresses you have per device on your local intranet. When we configure 'port forwarding' we're telling your router to take the ports we need on your computer's local IP behind the router and forward them to the ports exposed to the real internet as part of this NAT process. In this case this allows the tor relay we've configured to receive incoming connections on the port we've specified. Unfortunately this process is different for every router, but in order to provide an example I'll show what the changes look like for an Apple Airport Extreme and hopefully you'll be able to translate them to your own router's settings. First though we need to know your computer's local IP. Open System Preferences Click Network Click Advanced Click TCP/IP In this window you should see "IPv4 Address: XX.X.X.X" That's the address we need. Next open Airport Utilty (this is to configure port forwarding on an Apple Airport Extreme router) Click on the Airport Extreme Click Edit on the tooltip that pops up Click Network Notice the Port Settings Box, Click + Add the following settings: Description: Tor Ports Public UDP Ports: 9001, 9030 Public TCP Ports: 9001, 9030 Private IP Address: XX.X.X.X (this is the IP we found in Network) Priave UDP Ports: 9001, 9030 Public TCP Ports: 9001, 9030 Click Save Click Update (note the router will reboot) Note: This example shows the default ports we configured in our torrc, if you need to or decide to use different ports you'd have to configure the forwarding differently. I think only the TCP settings matter here, but I ended up setting both while trying to get this to work. Now we can set tor to launch on startup as well as start it right now with these two commands. {code} ln -svn /usr/local/opt/tor/*.plist ~/Library/LaunchAgents launchctl load ~/Library/LaunchAgents/homebrew.mxcl.tor.plist {code} Note: If you make changes to torrc in the future you need to restart tor. You can restart tor with the following command. {code} pkill -sighup tor {code} Now let's check out the logs and verify things are working. This command will show the end of the log and any new lines as they appear. {code} tail -f /usr/local/Cellar/tor/0.2.5.11/var/log/tor/notices.log {code} In a few mintues you should see the following lines if things are working: 19:29:38 [NOTICE] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. 19:29:36 [NOTICE] Self-testing indicates your DirPort is reachable from the outside. Excellent. If you see something like the following it's irrelevant: Apr 02 22:33:02.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. And if you see this it's not working (the X's here represent your public internet facing IPv4): Apr 03 17:10:41.000 [warn] Your server (XX.XXX.XXX.XXX:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Apr 03 17:10:41.000 [warn] Your server (XX.XXX.XXX.XXX:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. If you're still having trouble try hopping on IRC. ###

1 1

send me somerelays and bridges for vidalia
by Sh.F.M 04 Apr '15

04 Apr '15

1 0

Re: [tor-relays] multi-instance Tor support for *BSD packages
by Nusenu 03 Apr '15

03 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Pascal, thanks for your feedback. Pascal Stumpf: >> Multi-instance support isn't something that's provided by >> OpenBSD's rc.d(8) subsystem, and I doubt it ever will be. Too >> much complexity for something that's more of a crutch to work >> around few applications' limitations than something universally >> needed and useful. Ok, my take away here is that I won't be able to get any multi-instance support into OpenBSD's tor rc.d script. So I guess the next best option for ansible-relayor will indeed be to configure multiple services and copy the rc.d script of your package once per tor instance tor0,tor1,... plus one line per tor instance in /etc/rc.conf.local as described previously here: https://lists.torproject.org/pipermail/tor-relays/2015-March/006526.html >> Btw, aren't there locking problems with the files in >> DataDirectory? Or does every single tor instance need its own? >> And the ControlPort? One for each instance? How do you >> distinguish tor instances when doing syslog logging? ansible-relayor takes care of this and generates torrc files accordingly (separate datadir, separate logfiles, ...). regards, Nusenu -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVHuGbAAoJEFv7XvVCELh0nz0P/i0KffWajNLbBv0cHF5BB5V2 BgQAIDyy/UpSGXNkiUShOBvQIW1GhjvpX9UJeAVzBy2nJuAN8v+AEKp+9A7w4fLt qBxsgul0iaWSalrzlzGFu85QRrc31MV4MKUMW6HmBoINKwMZ71cbWqcmWwykzhOr VPjxrEzCcIw2FF42G2rd65ivWJVWueJLUlbN4KvhzP0clYbOMlgAZ4smstdIksbp pd13/AdA1aJGdCs+i4pXgd19Jq+7WG6Eqj7+YSEpk3LOxqiaVBAi0MhHH5J8be57 GKyI/9QI4yfgAYhtDyEZOVaslafgSAaMzniYYfmGDAPzZobKBbhwmXxtmnok7A30 4TMpUPiqYpVvhBu+NHqlhngYDvKJj/KoZb3lySyN5wMpi5gTtUIt1QxxQ6ofP0eW LuCQSJhinTuLehWx2Ib/gx+J2g+BqJeHkBZRt2BjL63RxHMiRJ3qy7Xd0mJlsh5t DPPPzovk6yaNRUNv7GDTTaq4vRSwJzfUikm9upUi+J37CJ1L3wo/xYqcqLHKWz/w 3NtoMi9mkJfjJ0Bx5ORDzeWJ6LtTKPmhQuWP+5PiK0CxEiu/ZVuReElKyz0Pnypa qrIji5vpu+w/ITw4E/IpMZYS/p/SZV+HYG/ffLUZNgJ6i6vHNqc7om6c+0Qp9qut Eax3QbcU8mCR+F8d2WmL =YcuY -----END PGP SIGNATURE-----

1 0

multi-instance Tor support for *BSD packages
by Nusenu 02 Apr '15

02 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Tor package maintainers for FreeBSD and OpenBSD, I wrote/I'm writing an ansible [1] role for tor relay operators [2]. Besides supporting Linux I'm also aiming to supporting OpenBSD and FreeBSD. Tor does not scale well across multiple CPU cores, to work around this issue relay operators frequently choose to run multiple tor instances on a single host. To better support tor relay operators with this common task tor's official RPM packages recently got multi-instance support [5] and a ticket for the official debian package has been filed [6]. To better know how to proceed with my ansible role - where multi-instance support is a core feature - I'd like to know how you think about adding easy multi-instance support to your packages as well? One way to configure a BSD system to run multiple tor instances would be to defined multiple services tor0, tor1, ... [3], but that doesn't strike me as a particular clean solution [4]. What do you think about supporting multiple tor instances with a single rc.d script that starts one tor process per available *.torrc file in (/usr/local)/etc/tor/enabled/ ? looking forward to your comments, Nusenu [1] http://docs.ansible.com/ [2] https://github.com/nusenu/ansible-relayor [3] https://lists.torproject.org/pipermail/tor-relays/2015-March/006526.html [4] https://lists.torproject.org/pipermail/tor-relays/2015-March/006527.html [5] https://trac.torproject.org/projects/tor/ticket/14996 [6] https://trac.torproject.org/projects/tor/ticket/14995 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVHZZ6AAoJEFv7XvVCELh04/IQAKZfuYvXUM4xkc3cS3GJciGg NsbkyL483NLM7un/gd0HNkUTzOVLMwI6gkzUERg5uYiwWD1ZHEnudrOk47N19FHR 7WjDTQQuKDfDBpMCBiAywFXsJKKnRk0Cg01+zmMlCmPZ5kEk1hyaE64sZNmjBLyQ 7ydLMV9/xy7h/qm7OfOjU9djoPQTbnd5Ky8+V15ZyTwr65IkWI6vX5KlIfhdTvHh sl3PlRppCE1aYPF5jbwSwpICOSd4diLWToFfOSDFRfvpc4FdMiJfIdAXj37FktMA RdI4MTJXRanLj7WVwKua8Gf2Za8my2t2mCTD3loFR1tRPE30uA1xul9eii+zp27n NBvSsSIhdVKcn1qK7lUfHIxa0v2ArzIjgBczHh6KzlS0U5Fd6LYqx+Y7sRSkjBlr nULJ2Bs+EqcjBF3OTjQFNG+dg/96QgIK+f7nVp/pvoGPKCDxiIdnuT7wlueguI9r Ys/7wCTOSTyrk7+q6IxYrliPReahTlK80HkMtba5m4JpBlGlikMtZcgVYeEuyeac fVfe/TcLjOkqFIomVpkhbtRDHJafu9Q5cMm/6eydXAH4y9GhM/Q6N+zEp4nXuSP3 /LzNFhwuFSabTwlnDx/5VpSXVYP+cmMoK9tWQjORNM//1zRONOea43eXeyhuwipo mTv/uEMpR9eDdPAJseod =ft3h -----END PGP SIGNATURE-----

1 0

Re: [tor-relays] Keep smiling only - i dont expect any answer
by Teófilo Couto 01 Apr '15

01 Apr '15

Same old, same old story, again and again... "They" operate badly developed, badly implemented "sites", full of well known vulns, but the issue, the "bad guy on set," is a tor relay... Typical... -------- Original Message -------- Subject: [tor-relays] Keep smiling only - i dont expect any answer Time (GMT): Apr 01 2015 14:02:00 From: cmar433(a)yandex.com To: tor-relays(a)lists.torproject.org nice abuse :) From: isac(a)kftc.or.kr To: abuse(a)wedos.com Date: 01.04.2015 08:42:07 Subject: [KF/ISAC] Warning! Unauthorized Access Trial! Dear Network Manager : I am a network security manager of Korea Financial Telecommunications and Clearings Institute(KFTC). My job is to protect Korean financial organizations from illegal intrusion attacks. We have received a report of unauthorized access trial originating from your site as shown below. -------------------------------------------------------------------------------- Date/Time(GMT+9): 2015-04-01 12:47:46 ~ 2015-04-01 12:47:46 Source IP : 37.157.192.208 Destination IP : 59.11.68.197 Attack Type : FCKeditor_Vul -------------------------------------------------------------------------------- We are seriously considering notifying these illegal attempts to the related authorities of both your and our countries and requesting proper legal actions. So, please take appropriate measures to identify and stop the attacker. And, please inform us of the results. (isac(a)kftc.or.kr) Thank you for your cooperation. p.s. : If you are not the correct person to deal with this incident, please forward this to the proper person and inform us for future convenience.

2 1

(no subject)
by Franck Marcel 01 Apr '15

01 Apr '15

Re

3 2

New relay not recognised by weathermap
by Sharif Olorin 30 Mar '15

30 Mar '15

Hi all, I configured a new relay[0] yesterday, and recently tried to sign up for the Weathermap[1], wherein I get a "could not locate a Tor node with that fingerprint" error message. The node's definitely been up for more than an hour, and Atlas can see it[2]. Is this expected behaviour, or might it indicate an issue with my configuration? I've checked everything on the "potential problems" list - the node does exist, the fingerprint is correct, it's been up for more than an hour, hasn't been down for over a year, and running a recent (0.2.5.11) version of Tor. Thanks, Sharif [0] dendrocyte.wiredlaboratories.com.au/03B5C7B81CA56DF3CCC31FDA8032A7763B8B50B4 [1] https://weather.torproject.org/subscribe/ [2] https://atlas.torproject.org/#details/03B5C7B81CA56DF3CCC31FDA8032A7763B8B5… -- PGP: 6FB7 ED25 BFCF 3E22 72AE 6E8C 47D4 CE7F 6B9F DF57

2 4

New relay not recognised gy weathermap
by Sebastian Urbach 30 Mar '15

30 Mar '15

Sharuf, I completely forgot to welcome you and thank you for running a relay ! So, welcome and i hope you stay for quite a while :-) -- Sincerely yours / Sincères salutations / M.f.G. Sebastian Urbach ----------------------------------------- Religion is fundamentally opposed to everything I hold in veneration - courage, clear thinking, honesty, fairness, and, above all, love of the truth. ----------------------------------------- Henry Louis Mencken (1880 - 1956), American journalist, essayist, magazine editor, satirist and critic.

1 0

Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge
by jchase 30 Mar '15

30 Mar '15

Thanks for your answer. Your instructions were good and explicit, but you hit on two of the problems I run into. I installed tor 0.2.5.11-1 from torproject.org and got two error messages that I couldn't solve. I would have to go back and re-install 0.2.5.11-1 to tell you what they were. In any case they weren't configuration problems. I had pretty much the same problem months ago when I installed a tor 0.2.5.x on Pi. Which leads me to want to use a raspbian repo. only I am unable to get /etc/apt/sources.list to recognize http://archive.raspbian.org/raspbian/pool/main/t/tor/ (or variations thereof) as a repository. And in my main raspian repo tor doesn't go any higher than 0.2.4.26 . So simply updating tor does not work. How do I add http://archive.raspbian.org/raspbian/pool/main/t/tor/ http://archive.raspbian.org/raspbian/pool/main/o/obfs4proxy/ http://archive.raspbian.org/raspbian/pool/main/libc/libcap2/ as one or more alternative repositories or force an install? Thanks, J. Chase tor-relays-request(a)lists.torproject.org: > Message: 4 > Date: Sun, 29 Mar 2015 00:19:14 +0200 > From: s7r <s7r(a)sky-ip.org> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge > Message-ID: <551728E2.4030705(a)sky-ip.org> > Content-Type: text/plain; charset=windows-1252 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi, > > obfs4 will not run on 0.2.4.x , you need at least 0.2.5.x or 0.2.6.x > > First, upgrade your Tor. > > You can use torproject.org repositories. If you are running wheezy: > > 1. Add the repository: > # echo "deb http://deb.torproject.org/torproject.org wheezy main" >> > /etc/apt/sources.list > > 2. Add the signing key: > # gpg --keyserver keys.gnupg.net --recv 886DDD89; gpg --export > A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add ? > > 3. Install keyring: > # apt-get update && apt-get -y install deb.torproject.org-keyring > > Now upgrade your Tor, an apt-get -y install tor would upgrade to 0.2.5.1 > 1. > > You can install obfs4proxy from deb.torproject.org too: > > # echo "deb http://deb.torproject.org/torproject.org obfs4proxy main" >>> >> /etc/apt/sources.list > # apt-get update && apt-get -y install obfs4proxy > > Now, modify your torrc to enable the obfs4 transport. Make sure you > also add ExtORPort auto in torrc so it will report some useful > statistics. obfs4proxy also supports obfs3, and some users still use > that, so if you can be an obfs3 and obfs4 bridge at the same time > (requires just one more open port) it would be great. > > Sample torrc entry for enabling obfs4 and obfs3: > ExtORPort auto > ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy > ServerTransportListenAddr obfs3 [::]:port > ServerTransportListenAddr obfs4 [::]:port > > To make the bridge even better, you can bind obfs3 and obfs4 to lower > ports (< 1024), if you have them free, such as obfs3 on 80 and obfs4 > on 443 (for example). This will help users behind really restrictive > firewalls who only allow connections on few ports. You can easily do > this with libcap2-bin package: > > # apt-get -y install libcap2-bin > # setcap 'cap_net_bind_service=+ep' /usr/bin/obfs4proxy > > To make this persistent after a reboot, edit the /etc/rc.local file > and add this line before 'exit 0': > setcap 'cap_net_bind_service=+ep' /usr/bin/obfs4proxy > > Hope this helps. If you don't want to use deb.torproject.org, > everything required is also included in raspbian main repo: > > http://archive.raspbian.org/raspbian/pool/main/t/tor/ > http://archive.raspbian.org/raspbian/pool/main/o/obfs4proxy/ > http://archive.raspbian.org/raspbian/pool/main/libc/libcap2/ > > If you want to use raspbian repo, simply ignore the lines where you > add deb.torproject.org to your sources.list file and just upgrade, > install the required packages and modify your torrc file. > > Thanks for running a bridge.

4 3

MY IP adress on blacklist and then in exit relay policy
by Cmar433 30 Mar '15

30 Mar '15

https://globe.torproject.org/#/relay/9DCF76179FCF47224D235ECD4A6165FED22ECE… So, i am running exit node. My provider send me an email .. "This IP is infected with, or is NATting for a machine infected with s_downloaderbot-mxb" Any idea what can i do with this problem ? Now i can see my IP in my server exit policy ... After my "delist action" is clean .. http://www.senderbase.org/lookup/ip/?search_string=37.157.192.208 I need just wait ? And all outgoing packet from my server still droped ? Thanks ..

5 7