December 2014 - tor-relays - lists.torproject.org

Possible DDoS
by Christian Burkert 26 Dec '14

26 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi *, I'm running a non-exit Tor node for a few months now on a virtual server hosted in a professional datacenter. That's the node: https://globe.torproject.org/#/relay/4C246EA9C950B872FD77F761CEAAB41D93D976… Yesterday, December 25th, the support wrote me, that my server is under a DDoS attack with 2GBit/s lasting over more than two hours. So, the hoster black holed my traffic to protect the other customers. The hoster wanted to know which services I'm running and told me that if I continue running Tor and further attacks will happen, then I would have to bear the costs. Eventually, I took down the Tor node to avoid further confrontation. Now I seek for your interpretation of this event: - - Has there been more recent incidents against Tor nodes? - - How can I investigate it? - - How should one react to a hoster? I mean they could have made up the whole thing... Looking forward to your comments Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCgAGBQJUnUdDAAoJEHAzZ6ooPDSy0nMP/1lyHPPFBxpAOvEiWL+ijrvA SPViJvZH/cPUS/11M7qm+bsZa/fbiRk6kY8ADcY8abe1Z8lHzMYPGwZvKaIijiZG M8hjCHtMWLipO6iLmVfFskDtRn37Ga2ibEhGkVesDV53kPcotgg4i7tIqIuNb11X Gnkk+WpYwkrS9nPZjYNLmce093s4lux/N5GyRY/gQii+h9mfDJ++W+1ueNU94UQ0 bvK1wF7MdicWlu0kR49hCgFtDFh7uUjP87MPZmmQYHI82qWhTJxqOuuImrnJew2k pCFSzn03x/hXg1QFNPNLsqHU9OhUob3/z17Azcpbir15mY4/YE7Gq14/LBM+FKh0 LqGjzaVbQo0hs0kE2yFk5sEP0Dsv5aiOUItqFIMTG52FYZ6cUh/eTxMd6vblHwfU ujil0rFCRqtmbF6wIDBuXDxc0fmdaRMWTDfSlPxYGkfUaq1tSea1OAvjFpheOcNM wu9QiTSq9BTLY010iHSYQDknSr+gFkc/ooNLsPV1AAZFyMlG0epLww6tqR7C9hZq RyEX9piqGal7mU56gETxhDrD0Z/aKgXMbS+KvYfZhopGWEVg5vbWPGxAId53nhr6 hjvLyFmy68hBdbOB/pvp8qvw8veQR3niiHIxhxAl+BIQzXX45x0uVCPHFUpbbLp5 POIwpEJ46oaz7+cddAHf =TcPt -----END PGP SIGNATURE-----

4 4

Re: [tor-relays] Possible DDoS
by Sebastian Urbach 26 Dec '14

26 Dec '14

On December 26, 2014 12:41:51 PM Christian Burkert <post(a)cburkert.de> wrote: Hi, > I'm running a non-exit Tor node for a few months now on a virtual server > hosted in a professional datacenter. Thank you ! > Yesterday, December 25th, the support wrote me, that my server is > under a DDoS attack with 2GBit/s lasting over more than two hours. So, > the hoster black holed my traffic to protect the other customers. I've seen this behaviour from some ISP's before and it's rather sad. If something like this happens my ISP is taking care of it without disabling my systems. I'm just getting a note with all the technical information and that's it. > The hoster wanted to know which services I'm running and told me that > if I continue running Tor and further attacks will happen, then I > would have to bear the costs. > Eventually, I took down the Tor node to avoid further confrontation. That's interesting, they gave you some infos like the time and the amount but nothing else ? Seems to me that they're pretty clueless and are fishing in the dark. Another reason for their behaviour could be that they want to get rid of you / your Tor node. Threatening customers is really sad, sounds like they heard the word Tor from you and then concluded "oh, than he basically asked for the attack". > > Now I seek for your interpretation of this event: > - - Has there been more recent incidents against Tor nodes? Nothing with that magnitude on my end for weeks. > - - How can I investigate it? You can ask your ISP for their logs regarding that attack. Do you have any logs on your system, maybe from a intrusion detection or anything else ? > - - How should one react to a hoster? I mean they could have made up the > whole thing... If you are already considering this than i would recommend changing to another ISP, sounds like there is already some distrust. > > Looking forward to your comments > Chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Icedove - http://www.enigmail.net/ > > iQIcBAEBCgAGBQJUnUdDAAoJEHAzZ6ooPDSy0nMP/1lyHPPFBxpAOvEiWL+ijrvA > SPViJvZH/cPUS/11M7qm+bsZa/fbiRk6kY8ADcY8abe1Z8lHzMYPGwZvKaIijiZG > M8hjCHtMWLipO6iLmVfFskDtRn37Ga2ibEhGkVesDV53kPcotgg4i7tIqIuNb11X > Gnkk+WpYwkrS9nPZjYNLmce093s4lux/N5GyRY/gQii+h9mfDJ++W+1ueNU94UQ0 > bvK1wF7MdicWlu0kR49hCgFtDFh7uUjP87MPZmmQYHI82qWhTJxqOuuImrnJew2k > pCFSzn03x/hXg1QFNPNLsqHU9OhUob3/z17Azcpbir15mY4/YE7Gq14/LBM+FKh0 > LqGjzaVbQo0hs0kE2yFk5sEP0Dsv5aiOUItqFIMTG52FYZ6cUh/eTxMd6vblHwfU > ujil0rFCRqtmbF6wIDBuXDxc0fmdaRMWTDfSlPxYGkfUaq1tSea1OAvjFpheOcNM > wu9QiTSq9BTLY010iHSYQDknSr+gFkc/ooNLsPV1AAZFyMlG0epLww6tqR7C9hZq > RyEX9piqGal7mU56gETxhDrD0Z/aKgXMbS+KvYfZhopGWEVg5vbWPGxAId53nhr6 > hjvLyFmy68hBdbOB/pvp8qvw8veQR3niiHIxhxAl+BIQzXX45x0uVCPHFUpbbLp5 > POIwpEJ46oaz7+cddAHf > =TcPt > -----END PGP SIGNATURE----- > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -- Sincerely yours / Sincères salutations Sebastian Urbach ----------------------------------------- Definition of Tor: 10% luck, 20% skill, 15% concentrated power of will, 5% pleasure, 50% pain and 100% reason to remember the name! -----------------------------------------

2 1

Tor Weather doesn't register my fingerprint
by Giovanny Andres Gongora Granada 26 Dec '14

26 Dec '14

Hi, Today I decided to run a Tor Relay and contribute to Tor Project on a Rackspace that I have free for it. I want to use Tor Weather to get notifications about my relay, but when I try to register my fingerprint it doesn't accept it. What could be needed to register it? My fingerprint is: 4C90453B94DAC00BE356283F427CECE024B9D224 This is the info about my relay: https://globe.torproject.org/#/relay/4C90453B94DAC00BE356283F427CECE024B9D2… Regards, Gio -- Mozilla Hispano: http://mozilla-hispano.org Mentor en mozilla-hispano.org: Gioyik <https://www.mozilla-hispano.org/documentacion/Usuario:Gioyik> Mozilla Colombia: Miembro en MozillaColombia <http://mozillacolombia.org/our-contributors/> twitter: Gioyik <https://twitter.com/Gioyik> Blog: gioyik.wordpress.com irc: gioyik

2 1

iptables
by mikael 24 Dec '14

24 Dec '14

Hi, I don't know what to do. Please help. I'm getting the following warnings in arm: 16:13:15 [WARN] Your server (MY_PUBLIC_IP:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. 16:13:15 [WARN] Your server (MY_PUBLIC_IP:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. My iptables rules are: mike@host:~$ sudo iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 127.0.0.0/8 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED REJECT all -- 62.210.140.93 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 62.210.151.213 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 103.41.124.106 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 103.41.124.112 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 109.230.220.135 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 115.84.179.148 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 117.21.225.176 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 188.116.19.109 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 219.232.239.40 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 221.235.188.214 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp spt:53 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp spt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9001 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9030 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:6881:6999 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:6881:6999 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8 LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `iptables denied: ' REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0

2 2

Whitelist
by Thomas White 24 Dec '14

24 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Directory Authorities, Can you please remove the following fingerprints/IP's from the blacklist as per my previous updates in tor-talk. D78AB0013D95AFA60757333645BAA03A169DF722 6F545A39D4849C9FE5B08A6D68C8B3478E4B608B 5E87B10B430BA4D9ADF1E1F01E69D3A137FB63C9 0824CE7D452B892D12E081D36E7415F85EA9988F 35961469646A623F9EE03B7B45296527A624AAFD 1EA968C956FBC00617655A35DA872D319E87C597 E5A21C42B0FDB88E1A744D9A0388EFB2A7A598CF 5D1CB4B3025F4D2810CF12AB7A8DDDD6FC10F139 1324EC51FBFA5FD1A11B94563E8D2A7999CD8F57 93CD9231C260558D77331162A5DC5A4C692F5344 IPs: 77.95.229.0/24 5.104.224.15 77.95.224.187 89.207.128.241 128.204.207.215 Authorities who haven't signed yet: gabelmoo tor26 maatuska moria1 urras Regards, T - -- Activist, anarchist and a bit of a dreamer. PGP Keys: key.thecthulhu.com Current Fingerprint: E771 BE69 4696 F742 DB94 AA8C 5C2A 8C5A 0CCA 4983 Key-ID: 0CCA4983 Master Fingerprint: DDEF AB9B 1962 5D09 4264 2558 1F23 39B7 EF10 09F0 Key-ID: EF1009F0 Twitter: @CthulhuSec XMPP: thecthulhu at jabber.ccc.de XMPP-OTR: 4321B19F A9A3462C FE64BAC7 294C8A7E A53CC966 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJUmfi/AAoJEFwqjFoMykmDLpwP/iRLkxYXMGzW4ohr/sG2nvYX Fitv6242N0NuGEFkwZgjaYEdiab4Afdg5xacu5r3+tzdccKawZX9w7NOpx1w8iXS IxO4i/nU5DhA2hyn/67/J/JBOqjVY7V0nXVtEOAK3NUGjiRK+uaSojfZ/y3iXgvv MHdr5eGM5Rj7/sZ2eqLsCdzSr0atGQXxyz2JhlVim5rZfG9ikzvGcv8PbDl67Fgp e5l/aq3NAHv8EiMAML1Wpah+hi7fDuyX4QcSLfrrwK2sv+oetbPSa6Kue26PP2Fr UKQLB412hJ4gtLFL5LiQXWvs1cuQO4Yw7tBOJ3qsh4kWpDtVUD7OTIDZRCK+FkwF FuH2XHwN8IVhIcQcTZ+I7dKqWi9vMxaJPWi15osah5rW48ozqCCSqFO9xICOyMDH V1JSeHTVzWCKpkpocUYzIMJvjuqADtAyuR9CX0hgEgUdGf9kMYdo+zGsiXomHO02 1iuWsq1HjwNxL2nAZJpCNsNetcHSvRtwGXbWx2Fr6P/T3tBh7gYfTSD2KwNnw+yE X0IDz5J02Xqz1nU2kiKr+IkZDXI+0aKzkD0KI6Uia0LEcZmjKNEePccHd+PcwIY/ YnH55rVyilUsLBvgQKZwGBVk+9kNmXjwiH1JJbUrGcfsCvZb+E05n5WMcbNYRwW2 N+2CQDnmN8aHLErrs5RU =zOpP -----END PGP SIGNATURE-----

2 1

help needed to setup a bridge on amazon and relay on PC
by Sasikantha babu 24 Dec '14

24 Dec '14

I've been trying to setup a bridge on amazon cloud and relay node on PC but never succeeded in setting it up. I always get an error "Your server (IP:9001) has not managed to confirm that its ORPort is reachable". 1. My PC is behind netgear router and I had configured portforwarding (portforwarding seems to work but tor-relay fails complains about ORPort reachability). 2. Follow the steps https://cloud.torproject.org/#get_started and created an instance on amazon cloud but facing the ORPort reachability. Dec 23 14:19:37.000 [notice] Bootstrapped 5%: Connecting to directory server Dec 23 14:19:40.000 [notice] We now have enough directory information to build circuits. Dec 23 14:19:40.000 [notice] Bootstrapped 80%: Connecting to the Tor network Dec 23 14:19:40.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Dec 23 14:19:41.000 [notice] Guessed our IP address as ip (source: ip). Dec 23 14:19:41.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Dec 23 14:19:42.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Dec 23 14:19:42.000 [notice] Bootstrapped 100%: Done Dec 23 14:19:42.000 [notice] Now checking whether ORPort IP:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Dec 23 14:39:41.000 [warn] Your server (IP:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Thanks

2 3

Tor Relay Operators Meetup at 31c3 *moved* - 28.12. 13:00
by Moritz Bartl 24 Dec '14

24 Dec '14

Hi, I had to move the meetup slightly in time and to a different room. I was told by CCC orga that they need the original room for Engel meetings. NEW DATE: 28.12.2014 13:00 LOCATION: HALL C https://events.ccc.de/congress/2014/wiki/Session:Tor_Relay_Operators_Meetup See you! -- Moritz Bartl https://www.torservers.net/

1 0

Tor Relay Operators Meetup at 31c3 - 28.12. 14:15
by Moritz Bartl 24 Dec '14

24 Dec '14

Hi, Torservers.net invites Tor exit relay operators and organizations to a meetup. If possible/relevant, for example if you're a member of one of the 'Torservers partner organizations', please prepare some slides on your activities. You're obviously also welcome to suggest sessions as a member of the broader relay community! We will do quick presentations on recent and future activities around Torservers.net, talk about events relevant to the Tor relay community, and what lies ahead. https://events.ccc.de/congress/2014/wiki/Session:Tor_Relay_Operators_Meetup 2014/12/28 14:15 - 16:15 See you there! -- Moritz Bartl https://www.torservers.net/

5 8

DDoS attack targeted on my exit node
by Michael Renner 22 Dec '14

22 Dec '14

Hi, my tor exit node was targeted with two DDoS attacks, one on 2014-12-20 01:00 CET and one on 2014-12-22 18:00 CET [1], both lasting about 5 minutes each. This alone wouldn’t be too noteworthy if it weren’t for the fact that a) there’s a certain state of alarm WRT the Tor networks integrity and b) these are the only attacks my ISP has on record for the over 2.5 years of operating the Tor Exit node. If no other operators have noticed anything out of the ordinary (given by the silence on the list) this is most likely a fluke (getting rid of pesky IRC users?), but better be safe than sorry. best, Michael [1] http://i.imgur.com/Zu9UkW3.png <http://i.imgur.com/Zu9UkW3.png> Summary screen

3 2

ntp needs attention
by Felix 22 Dec '14

22 Dec '14

Hi See: https bugs.debian.org/cgi-bin/bugreport.cgi?bug=773576 Debian will be fixed by 'apt-get update' and 'apt-get upgrade'. dpkg.log tells if the fix is in place: https security-tracker.debian.org/tracker/CVE-2014-9293 ... Cheers!

3 2