- tor-relays - lists.torproject.org

Relays by AS Names
by SuperSluether 06 Apr '16

06 Apr '16

I want to host an exit relay, but at the same time I don't want to use a service that already hosts multiple Tor relays. Is there a website that lists relays by AS Names so I can find a service that isn't already populated with Tor?

10 10

Blocking Tor - A case for more accuracy
by Eran Sandler 06 Apr '16

06 Apr '16

https://blog.perimeterx.com/blocking-tor-a-case-for-more-accuracy/ There are certainly other ways of handling Tor traffic and measuring the real intention of a user. Disclaimer: The guys at PerimeterX are friends of mine. I sent them the CloudFlare post (as well as the post from the Tor blog) because I know their methods are much better in detecting intention and not just blocking Tor IPs. Eran

1 0

Relay request
by runner7272 04 Apr '16

04 Apr '16

Sent from my Sprint Phone.

2 1

Re: [tor-relays] tor-relays Digest, Vol 63, Issue 5
by d3part3d＠tuta.io 04 Apr '16

04 Apr '16

? -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 4. Apr 2016 15:31 by tor-relays-request(a)lists.torproject.org: > Send tor-relays mailing list submissions to > > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Tor Weather has been discontinued (Karsten Loesing) > 2. Re: Tor Weather has been discontinued (Eran Sandler) > 3. Re: Tor Weather has been discontinued (Eran Sandler) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Apr 2016 16:48:39 +0200 > From: Karsten Loesing <> karsten(a)torproject.org> > > To: > tor-relays(a)lists.torproject.org > Subject: [tor-relays] Tor Weather has been discontinued > Message-ID: <> 57027EC7.9010802(a)torproject.org> > > Content-Type: text/plain; charset=utf-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dear relay operators, > > as of April 4, 2016, Tor Weather has been discontinued. > > Tor Weather [0] provided an email notification service to any user who > wanted to monitor the status of a Tor node. Upon subscribing, they > could specify what types of alerts they would like to receive. The > main purpose of Tor Weather was to notify node operators via email if > their node was down for longer than a specified period, but other > notification types were available, including one where operators would > be informed when their node was around long enough to qualify for a > t-shirt. > > The main reason for discontinuing Tor Weather is the fact that > software requires maintenance, and Tor Weather is no exception. Tor > Weather was promising t-shirts for relays that have not been around > long enough or that provided too little bandwidth to be useful to the > network, and it was almost impossible to deny a t-shirt after Tor > Weather has promised it. Apart from that, Tor Weather was likely not > offering t-shirts to people who have long earned it, thereby confusing > them. An unreliable notification system is worse than not having a > system at all. Relay operators shouldn't rely on Tor Weather to > notify them when their relay fails. They should rather set up their > own system instead. > > We have tried to find a new maintainer for Tor Weather for years, but > without success. We started rewriting Tor Weather [1] using Onionoo > [2] as data back-end in 2014, and even though that project didn't > produce working code, somebody could pick up this efforts and finish > the rewrite. The Roster developers said that they're planning to > include an email notification function in Roster [3]. And we > developed a simple Python script that provides information about a > relay operator's eligibility for acquiring a t-shirt [4]. None of > these alternatives is a full replacement of Weather, though. > > We encourage you, the community of Tor relay operators, to step up to > start your own notification systems and to share designs and code. > Tor Weather is still a good idea, it just needs somebody to implement it. > > Tor Weather is discontinued in two steps. For now, new subscriptions > are disabled, new welcome messages are not sent out anymore, and > existing subscriptions continue working until June 30, 2016. From > July 1, 2016 on, Tor Weather will not be sending out any emails. > > Sorry for any inconvenience caused by this. > > All the best, > Karsten > > > [0] > https://weather.torproject.org > > [1] > https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 > > [2] > https://onionoo.torproject.org > > [3] > http://www.tor-roster.org > > [4] > https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py > > -----BEGIN PGP SIGNATURE----- > Comment: GPGTools - > http://gpgtools.org > > iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 > WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF > xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE > ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i > gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER > VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= > =LVj8 > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 2 > Date: Mon, 04 Apr 2016 14:58:20 +0000 > From: Eran Sandler <> eran(a)sandler.co.il> > > To: > tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Tor Weather has been discontinued > Message-ID: > <> CALR3k-G0DoeRB-baVw+uvGUeMdDRVMORwEgAjDgCg6kE3n1cGQ(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > I have played quite a bit with onionoo and wrote a wrapper in Go for it. > > I am willing to rewrite Tor Weather using Go (or python if you like). > > I'll go over the old code and this email again to make sure I understand > the full scope of the project. > > As an operator I have relied on the Tor Weather alerts to know if one if my > nodes were down and while it's wasn't quick enough in sending alerts it was > a good tool. > > I have some ideas about the t-shirts alerts so that we won't miss sending > to those that need it and wouldnt send to those that don't need it. > > Eran > > On Mon, Apr 4, 2016, 17:49 Karsten Loesing <> karsten(a)torproject.org> > > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Dear relay operators, >> >> as of April 4, 2016, Tor Weather has been discontinued. >> >> Tor Weather [0] provided an email notification service to any user who >> wanted to monitor the status of a Tor node. Upon subscribing, they >> could specify what types of alerts they would like to receive. The >> main purpose of Tor Weather was to notify node operators via email if >> their node was down for longer than a specified period, but other >> notification types were available, including one where operators would >> be informed when their node was around long enough to qualify for a >> t-shirt. >> >> The main reason for discontinuing Tor Weather is the fact that >> software requires maintenance, and Tor Weather is no exception. Tor >> Weather was promising t-shirts for relays that have not been around >> long enough or that provided too little bandwidth to be useful to the >> network, and it was almost impossible to deny a t-shirt after Tor >> Weather has promised it. Apart from that, Tor Weather was likely not >> offering t-shirts to people who have long earned it, thereby confusing >> them. An unreliable notification system is worse than not having a >> system at all. Relay operators shouldn't rely on Tor Weather to >> notify them when their relay fails. They should rather set up their >> own system instead. >> >> We have tried to find a new maintainer for Tor Weather for years, but >> without success. We started rewriting Tor Weather [1] using Onionoo >> [2] as data back-end in 2014, and even though that project didn't >> produce working code, somebody could pick up this efforts and finish >> the rewrite. The Roster developers said that they're planning to >> include an email notification function in Roster [3]. And we >> developed a simple Python script that provides information about a >> relay operator's eligibility for acquiring a t-shirt [4]. None of >> these alternatives is a full replacement of Weather, though. >> >> We encourage you, the community of Tor relay operators, to step up to >> start your own notification systems and to share designs and code. >> Tor Weather is still a good idea, it just needs somebody to implement it. >> >> Tor Weather is discontinued in two steps. For now, new subscriptions >> are disabled, new welcome messages are not sent out anymore, and >> existing subscriptions continue working until June 30, 2016. From >> July 1, 2016 on, Tor Weather will not be sending out any emails. >> >> Sorry for any inconvenience caused by this. >> >> All the best, >> Karsten >> >> >> [0] >> https://weather.torproject.org >> >> [1] >> https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014 >> >> [2] >> https://onionoo.torproject.org >> >> [3] >> http://www.tor-roster.org >> >> [4] >> https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py >> >> -----BEGIN PGP SIGNATURE----- >> Comment: GPGTools - >> http://gpgtools.org >> >> iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 >> WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF >> xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE >> ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i >> gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER >> VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= >> =LVj8 >> -----END PGP SIGNATURE----- >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >

1 0

I would like to help.
by Generalgrievous 03 Apr '16

03 Apr '16

I have a Banana Pi that I would like to use to help the TOR network. I have installed Debian-Jessie and started researching the process for setting up relay, even an exit. I am a total noob, but willing to learn. If someone is willing to help me step by step, I would be excited to help. I've tested my internet speed, Download average 60 mbps, Upload avreage 6 mbps, If I would be more of a hindrance than a benefit, please say so, no hard feelings. Located Central CA. General G. Sent from [ProtonMail](https://protonmail.com), encrypted email based in Switzerland.

6 6

Earned T-shirt and no email response for months
by Dimitar Milkov 02 Apr '16

02 Apr '16

Hello, My relay earned me a Tor T-shirt a couple of months ago. I emailed the team responsible for them on the email given in the T-shirt descriprion page (https://www.torproject.org/getinvolved/tshirt.html) with size, shipping address and everything, and the notification email from Tor Weather also included. However, there is still no response. I asked in IRC after the first month or so and some people said that they are overloaded with work because of some campaign/conference sort of thing. How long it usually takes for a T-shirt request to be processed? What is your experience?

4 4

Re: [tor-relays] Relays with broken DirPorts
by starlight.2016q1＠binnacle.cx 02 Apr '16

02 Apr '16

These relays all appear at least somewhat overrated by BWauths and are not rate-limiting with BandwidthRate. DirPort performance is bad due to a saturated physical link or 'tc' bandwidth limit, so TCP congestion back-off kicks in. If BandwidthRate were the limiting factor DirPort would return a 503 (busy) error. Reason for the overrating is a serious bug in Torflow resulting in relays going unmeasured for extended periods, possibly more than 30 days at which time a BWauth will cease listing an affected relay. I'm planning to work on fixing this, but have not had the time and presently don't see getting to it before early summer. >Dear Relay Operators, > >Also while working on #17158, I found some relays whose DirPort >responses made my python script hang. It wouldn't even respond >to ^C, but that might just be an OS X thing, or a stem thing. > >I'm not sure what to do about these relays. I'd like to do a >tcpdump / Wireshark check, but I don't have time at the moment. >Would anyone like to follow this up? > >This is an incomplete list of broken relay IPs and DirPorts, >starting with those with the highest consensus weight: >217.23.14.190:1194 >151.80.164.147:80 >148.251.255.92:80 >78.142.19.59:80 > >Thanks > >Tim > >Tim Wilson-Brown (teor)

3 2

Relays with very slow DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

Dear Relay Operators, While I was checking fallback directory mirrors for #17158, I encountered some relays that took more than a minute to serve a consensus. Most took 150 seconds, which could be caused by a RelayBandwidthRate of 10 kilobytes a second. One solution to this issue is to disable the DirPort on relays with a RelayBandwidthRate less than 50 kilobytes a second, or more than 30s to serve a consensus. https://trac.torproject.org/projects/tor/ticket/18688 (This ticket also contains the python / stem code that I'm using to check the consensus download speed.) But I don't actually know if it's the relays' torrc configuration that's causing the issue, or if their provider is limiting their speeds, or if there's some other issue. If you're the operator of one of the relays listed below, can you let me know? And if someone wants to investigate further, or contact these operators on their ContactInfo, that would be great. (I don't have time right now, I'm trying to pull together a list of fallback directories before the 0.2.8-rc.) This is an incomplete list of slow relay IPs and DirPorts, starting with those with the highest consensus weight: 217.198.117.122:80 212.47.250.44:80 158.69.112.86:80 50.7.178.34:80 191.101.251.172:80 51.254.249.177:80 188.165.232.40:80 104.236.38.231:8080 89.163.225.184:9030 185.31.230.69:9030 81.7.14.227:9030 62.210.238.33:9030 164.132.56.137:9030 212.107.149.145:9030 94.23.165.33:9031 Thanks Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 1

Re: [tor-relays] Relays with broken DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

> On 31 Mar 2016, at 11:23, Michael McConville <mmcco(a)mykolab.com> wrote: > > You'll probably get through to more people if you include nicknames with > IP addresses, and if you send an email to the operators who listed their > address in ContactInfo. I was actually hoping that someone else would do that for me, I'm a little snowed under at the moment. Tim > > Thanks for this, > Mike > > Tim Wilson-Brown - teor wrote: >> Dear Relay Operators, >> >> Also while working on #17158, I found some relays whose DirPort responses made my python script hang. It wouldn't even respond to ^C, but that might just be an OS X thing, or a stem thing. >> >> I'm not sure what to do about these relays. I'd like to do a tcpdump / Wireshark check, but I don't have time at the moment. >> Would anyone like to follow this up? >> >> This is an incomplete list of broken relay IPs and DirPorts, starting with those with the highest consensus weight: >> 217.23.14.190:1194 >> 151.80.164.147:80 >> 148.251.255.92:80 >> 78.142.19.59:80 >> >> Thanks >> >> Tim >> >> Tim Wilson-Brown (teor) >> >> teor2345 at gmail dot com >> PGP 968F094B >> >> teor at blah dot im >> OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F >> > > > >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 1

Relays with broken DirPorts
by Tim Wilson-Brown - teor 31 Mar '16

31 Mar '16

Dear Relay Operators, Also while working on #17158, I found some relays whose DirPort responses made my python script hang. It wouldn't even respond to ^C, but that might just be an OS X thing, or a stem thing. I'm not sure what to do about these relays. I'd like to do a tcpdump / Wireshark check, but I don't have time at the moment. Would anyone like to follow this up? This is an incomplete list of broken relay IPs and DirPorts, starting with those with the highest consensus weight: 217.23.14.190:1194 151.80.164.147:80 148.251.255.92:80 78.142.19.59:80 Thanks Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

1 0

Tor Exclude Nodes Misbehaving
by stealth＠nym.mixmin.net 30 Mar '16

30 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have edited my torrc file on my Tor Client to exclude several countries, but I keep getting the United Kingdom in my pathway. My torrc file is below: DataDirectory C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor GeoIPFile C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip GeoIPv6File C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip6 ExitNodes {PL}, {RO}, {LU}, {DK}, {CH}, {NO}, {AN}, {LI}, {IS}, {FI}, {NL}, {HU}, {BG} ExcludeNodes {US}, {CN}, {FR}, {UK}, {ES}, {IT}, {AU}, {HK}, {RU}, {PT}, {IL}, {IE}, {DE}, {CA}, {BE}, {NZ}, {PR}, {MX}, {KP}, {KR}, {GR}, {DJ}, {JP} StrictExitNodes 1 When I click on the green onion after selecting a web site, I keep getting the United Kingdom as one of my nodes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW9eAMAAoJEH1gNwhiMDZusekP/jXnkAkTIHEvytXkoRsPKvYv NY9DG0eX/n6nE4ufBAczoRgaZMCwF5BPlBio9CyiSlL4qiI0xZ9zqY1vV5+kIrYS cewQH62JvS2rj3DRykVytyHXrdRE+zvnhqqY0fqD/7+WehXkG9dQmu5TT8qfmS35 bw12EpVs6yyAR7Rfhnaha0D1fqK1ekOFkpi+bo6j7X6LMW6zPnWhzROZeqEakFtP slcGJlF+OIk2f2pTkYzhq5MHwollZ+bUqkljFLzvzl1HvK2lHMtLLSgnLcU/88hC 7bhJiOfkh7+jmpi+GMzoCRFGWLq75bufJ34acxap3P4bRnYduJ72RvUQ40+LITcj dNmtFTC/+psrdvjHBJP9XDO8FPhmVIOlEr588tjgOPQwDNHbe5t7TMEYk/8S5EzH +7ahYd9MbT03oNnVrQKbSut66LmuukDyIuvR8gP9UU2+VNmKubxVcsRlOQvDmIDR /zqT6nYrc7uCimE37Ny0K8v2R0NSwE/rVPZeP2i0dzgyHOkSPLitRDvkyLgDI+kr Wwn0cAkdzjs4428PdOnEyu+b2vLtXDcV3Q1aH32wQbMXR/o2uaY4VB6iVTjU6tlb bexKHehLYmaK0c0LKLb91mxjequDe4QEdJBUQg/vVvmwPzcvVBHXJgPmPf9uJ9W/ Szr3idQyUm4QZ6WvCAvD =FURP -----END PGP SIGNATURE-----

5 4

Who operates the bridge with nickname antirio?
by Karsten Loesing 27 Mar '16

27 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, does anybody here know who operates the bridge with nickname antirio? https://atlas.torproject.org/#details/16609212922F6F1077A1BBA299709E19F9A3F… I'm asking, because that bridge has a nice distribution of IPv4 and IPv6 clients: bridge-ip-versions v4=48,v6=64 bridge-ip-versions v4=56,v6=72 We have a bug where IPv6 addresses are included in bridge-ip-versions statistics but where consensus downloads via IPv6 addresses are not counted. It would be very valuable to test the patch for this bug on the antirio bridge or on another bridge with at least 1/2 of clients connecting via IPv6. (When looking yesterday I didn't find another bridge with that property.) The patch is commit b79d859 in my task-18460-2 branch: https://gitweb.torproject.org/karsten/tor.git/log/?h=task-18460-2 In theory it should be sufficient to cherry-pick that commit from any other recent tor branch. It just changes three lines of code. More details on the ticket: https://trac.torproject.org/projects/tor/ticket/18460 Thanks! All the best, Karsten -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJW94evAAoJEC3ESO/4X7XBs5UH/jTAcsuOl6sCJO21WuOLcMmI csq/b1IPsBvoh6YT8HBh4h07+mJSwMuWXcm3nReJsmdvjlDP4watlsEbqMgX+oxo 6GSSOX4ySS4C5bscywxXWvZIDFWPC6rToYcyfyFDmP5I+nkPNyVqsc9fBXjGJvpN uJ15bixc0iZaespKG6mQwgX8ZHi9Hf+s089voQyMEe09SscKqXHe3/50ZrLHmLPl d8BJ8Ij6WxD9ndG6FOVAUOoTunsWL8NbVSHSCJf93LOUsM6XmPjIPERyvcvnL54M uvg3kqIFTdngvLwFqzB4cETREnJtXuPIPMt8eAMLsDGtcDAuSZiqKhs1dEpJLQE= =7cQU -----END PGP SIGNATURE-----

2 2

Minimum Relay/Bridge Bandwidth
by SuperSluether 26 Mar '16

26 Mar '16

Our family recently downgraded our internet connection, which limited our upload speed to 1Mbps. According to the Tor relay doc, a minimum of 2Mbps is recommended, yet a relay is considered "fast" if it has 1Mbps. Will I be hurting more than helping if I run a relay on this connection speed? Should I run a bridge instead? SuperSluether

3 2

Weird relay outage
by Xza 26 Mar '16

26 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Suddenly my relay lost all it's flags plus weird bandwidth drops while the network is fully intact. Tor version 0.2.7.6 - Ubuntu server 14.04 - -- PGP : 29A4CE52 -----BEGIN PGP SIGNATURE----- iQI4BAEBCgAiGxxEbyA8eWFuZGVyZXNvbkByaXNldXAubmV0PgUCVvaCxAAKCRBI of/XNyszStdfD/9KFIGLcxSUS0gmfHjJFPEgxHqBYunI4wSehrSve+ZcA5D66u7J FaYDaA3BB3+q2OuDsz4/3yb2ArGObkzV6sTZi4ti1zT3knU11Zw7zYvtZ7kFnfjD BFz6N7wY1tu+crrBLmM53ycyURlZxMYQieK5bpgUdz4S8WBm9LIGN1A2uV6Ifnjc Hn7cke64b0iij5QVIp0v04CjzhhxywvYqcu5U/1Z/nnxt53bGW5gtaaacz4y0fVf qFVUaBXiJR0usxoX0yvE3t+qfGVyUNAHbbB4nO3tVxQJqqaOiGcqwLoMVDCbmQlm 2ZXnbC0dgA12votJVHthZ0EGNH75+IthGic/+3LvcDoalVruohNVhXNj5WJhe5w8 J8G8KDJ+ZgnOstDwd3yJnogX0BuFB3fovopMzuWf+AJB3MVODzDbTE2md4bk1/QT If1jLLLWxhVCJJg3f7WzM1+L8glo7NUVCS6rL1DXKiFpEHP2Gw9fo8HKYxwiPar/ wvVchOL3FimbphMqKBd9o1o8CeYB9VZFUMt+cm3tfRimpotn3WNgNOWJw2Udlvpu 9l+582Vs1Y6ebZ7KfKETmsbF6iI00tA/kX9MBJu0X6TICDK31vXHR77d5HvZ1Ql6 bv7u/QBeBmGiUCy/w5utq1RZ7MxO9MDtY22dkakim4nYw8fpJL3fgWjn1g== =Bo8A -----END PGP SIGNATURE-----

3 4

Tor Exclude Nodes Misbehaving
by stealth＠nym.mixmin.net 26 Mar '16

26 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have edited my torrc file on my Tor Client to exclude several countries, but I keep getting the United Kingdom in my pathway. My torrc file is below: DataDirectory C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor GeoIPFile C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip GeoIPv6File C:\Users\Myname\Tor Browser\Browser\TorBrowser\Data\Tor\geoip6 ExitNodes {PL}, {RO}, {LU}, {DK}, {CH}, {NO}, {AN}, {LI}, {IS}, {FI}, {NL}, {HU}, {BG} ExcludeNodes {US}, {CN}, {FR}, {UK}, {ES}, {IT}, {AU}, {HK}, {RU}, {PT}, {IL}, {IE}, {DE}, {CA}, {BE}, {NZ}, {PR}, {MX}, {KP}, {KR}, {GR}, {DJ}, {JP} StrictExitNodes 1 When I click on the green onion after selecting a web site, I keep getting the United Kingdom as one of my nodes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (MingW32) iQIcBAEBAgAGBQJW9uefAAoJEH1gNwhiMDZuNNMQAIXhg1yq0Fq4pC2PsQ5jrOSh AtI3CnsUYg1+CtzAQtqksfb7PDwhTVAXFu7l2Ap1PrPBc+LcFrzZ4HAbqTPpGaYP DPokmhIlTgAzgAmu0n7RDJPSJmFXRJWdW6wULI4GsAPFHE9gU036Hd+1R9agIxrt oleizTVRAXpFqQgjLtGfiIYGQUh5vlWIiVCWOr6CGE5GkWLOC5oYPU7wKDzIE25o 7L56y6AyiUcA7abRMCDQCnVQ2AAY4dZwJ8ESK+j+ZJMGZIK2CbBeJF2QwlkjSFdn Mtjbctl4qwQqgcBhcVKuK3dMsdVnpj1YqEa8mGeMVTje74R1E2HULsJHq1UPLvkr /h8HTspIf45KvcDL1F1PoHpr9B2zWW/LJxvBL2VJiNIDRjZscuIQdzNJe2GE3P51 ImUozWR1+BHhn0h+y9zq/Pcq0dlmHGdrf7v/QgSLPq9g5RbNsyRKA6j0KhIC9efX 71DVclpgwAVC9itgpEnc1wHMkZZwcs+JWYJjvgcJ2UFR/CY79ZWfQePAn2bCledN AOkBfDclPvKZMXy9cXh9SgPWTesonOp4CubhvFXH6ReBBWfU9RYjCRhqy9w6XPaB OiYObQEYgoodftNZoqo8HVDdHLq0S+mwUPEM2x1UQDga40F8LqR3SB0BKySalG6K Mlc+6qOy65PvE6OGt94Z =kUjp -----END PGP SIGNATURE-----

2 1

OrNetRadar spots botnet joining the tor network? (79 relays, 38 countries, 67 ASes)
by nusenu 25 Mar '16

25 Mar '16

Hi, this smells like a botnet to me: http://article.gmane.org/gmane.network.onion-routing.ornetradar/1073 http://article.gmane.org/gmane.network.onion-routing.ornetradar/1074 all relays with that bitcoin adress: https://gist.githubusercontent.com/nusenu/fb19034a7860dba6c203/raw/5531768e…

4 10

Starting an exit node from spain
by f4aRelay 24 Mar '16

24 Mar '16

Im spanish and i want to start a tor exit relay. I have thoght about using this hosting: Pulse Servers (http://www.pulseservers.com/) Also i would like to know if there is any legal thing i should know for running a relay in spain Thanks -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQENBFb0BYIBCADE1jSLjOOb0sVZBAHpbItjWoqJamG+mlrR4936upHz2m2r7D2L pzOoYF/Gn4Iytk3IGVZT3Hfci18+nymidYl0L9guGLYGU1Z/T+v7wFKMOJCbty6p TNm9lOYDc1d8AVEGMMj2rmcHwP2ON98CRxKgGJscVgA7xno2PVeQSGqBgLv2UB/0 rqZsJnbsSHPH9+qxfxNuNh8DoByClf2S/Fx/WYbqyaoJBofv7FAVjWSVJTB/KSBO 2rDt9IRD3cLnFjGsGS7MBPvimPPgJQRkPrXPTWP3v5RNvUhd03PkLcPEcKF1fans MR1ywzxGxMQninSLw4oxpTm5H5xfqDfmRH/tABEBAAG0IkY0QXJlbGF5IDxmNGFy ZWxheUBwcm90b25tYWlsLmNvbT6JATkEEwEIACMFAlb0BYICGwMHCwkIBwMCAQYV CAIJCgsEFgIDAQIeAQIXgAAKCRCG6H1KC64jxZOhCADEHjEI+XkhmsNd67NjywIw aiaIfClVOrr5qnwhmZ77Wz7cmOcUsVJCNiKeYcG7WSOhNLeVEg7F6qeLyne5VHnJ Ncbb7+6YeD2bz04PcwDAyrkWRYdKhjIuNxbx1qoMzTkuenXa6qd+hj4yObYJlful 3zw5x49Vky6lxU3rHL+pKq2F2Hb6fyOkJd9uXP/I1muk98GMWK3WcLXGGY0TRo+7 CrlCvZBCtJ6laOo9hmt25KiuYq8xctT5Y7G3W+xc8yva0rQ+7D3wrCjFZIZAk6qt isn65zKBaGaTeMn+OfzWAsLsNyXCqvUT3BqQ4gd6Iu4VFtpWgetc1CehMkgaptYW uQENBFb0BYIBCACu2eXrkf+E1OE3zzXlJkG8GSL16F7qlOSqmezYGyJiPjLCSSiS WhG5s/7vbP90iM/LT9MRWExeae4JFesobPjt3TWF6vJflIL168uc6H8uKoncFET8 yN6eaayGNnhLYNef4dd+2qvU91qKZke1rRkBb7KQRUN7lTmFGOdsbYXk1OcUfS/p uZeF2QfdKhanWuDl42oQz+aB69UcDwwPbwplb329wR/I7AV+KFr1qTIIilq6qRek xOQOqzVF8mBMVS5EMjr3SQZaK9Ch21njZJr3pQ+hLI5RAx8a6k8vHn8muJEFxDTo hcPuOJ1Z8eBNKs7HA/XypJr56DCYt9nHE6GhABEBAAGJAR8EGAEIAAkFAlb0BYIC GwwACgkQhuh9SguuI8VNuQgAnuAN6UfxN55bCaTNWwJA0hietSNjKlM1TEzmjHmR 4Ch18lW2o4DT2dxCyoC+tRCjrLOxeKl7+MxGRF3mVl1tHSasjFkWFd6BohFutlJd 8r52RvdR2cPgEY+R9VLw6onQFEyMiTKxypwrCMKrB+R5qH6AvrBkGMjfZDdTqybi 8Kq4ZpqomnIsK85X+Kvr9SKuk4j4dkh244kk/8GAsZqhSKyP8D4JnylAhD/ZTSiT nXsXs0QIi1fntt6xxVx72UgR0pKEyl2koN76Mvew8qSZBALyp+o1cqaFOQXsO+gt Ri2gEEfL7Eors/Nl2+BGCHcWHXhY9F4nNz6fsq5DN+2Wzw== =LfjJ -----END PGP PUBLIC KEY BLOCK-----

3 2

Re: [tor-relays] Minimum Relay/Bridge Bandwidth
by Michael Armbruster 24 Mar '16

24 Mar '16

> Our family recently downgraded our internet connection, which limited > our upload speed to 1Mbps. According to the Tor relay doc, a minimum of > 2Mbps is recommended, yet a relay is considered "fast" if it has 1Mbps. I think you misread the documentation. 2Mbps is a recommended minimum, but a relay is considered fast if it has 1 Megabyte/sec and Megabit (Mb) and Megabyte (MB) are not the same. > Will I be hurting more than helping if I run a relay on this connection > speed? Should I run a bridge instead? With 1Mbps, you have 125 Kilobytes/sec upload rate. I would say yes, run a bridge instead. But let's see what other pepole say, eventually. Michael Armbruster

2 2

intense DDOS of exit relay from China
by Dhalgren Tor 22 Mar '16

22 Mar '16

FYI tor-relays Exit was DDOSed yesterday at 18:00 UTC. The attack was intense enough that the ISP null-routed the server for 16 hours, which has never happened before. Have seen a handful of brief DDOS attacks (about 15 minutes) in the past but none were so intense as this one. All traffic originated from China.

4 3

Running 5000 relays...
by nusenu 21 Mar '16

21 Mar '16

Moritz wrote: > Maybe this is better taken to tor-relays. Ok. url to the tor-dev thread: https://lists.torproject.org/pipermail/tor-dev/2016-March/010473.html Brian didn't say anything about planed deployment locations, but if _all_ relays are within a single /16 network you might skip MyFamily altogether, but I assume they are not. > In my case machines have a lifecycle. They come and they > go out of curiosity: What percentage of them do you expect to be online concurrently? (starting when) Are planing to rekey when "coming back" or resume with the former? > On 03/05/2016 10:31 PM, Brian "redbeard" Harrington wrote: >> "Lets say you are about to deploy 100 relays within the next week." - >> Take this an order of magnitude greater and we're on the right track >> with the correct scale. It is a regular occurrence for our users to >> deploy 500 to 5000 nodes at a time. This is why I said "and maybe set yourself an upper boundary as to how big you want to grow" A single entity deploying 5000 relays isn't very sane at the current network size I guess, but instead of speaking of relay counts using CW fraction/exit/guard probability as upper boundaries makes more sense. <10% might be a worthy upper boundary for exit/guard probability. The biggest (known) exit operator is currently at 7-8% exit probability. teor wrote: > And there's likely some limit on MyFamily or on descriptor size that would stop > you listing 1000 fingerprints. That is actually another good use-case for replacing the current MyFamily design with something that scales better with family size like Mike's proposed design (#5565), but we did not see declared families that big so far. It was no problem in practice. https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n364 > Server descriptors may not exceed 20,000 bytes in length; [...] If they do, the > authorities SHOULD reject them. So the max family size would be something around 400 relays? (20000 - 1250) / 42 = 446 (1250 bytes was the size of a non-exit sample descriptor without family) > generating 1000 relay keys and coordinating that key > distribution dance across the same number of nodes (more than likely in > highly distributed environments) seems to bring more questions than it > answers (securing the keys for those nodes, securely distributing them, > etc) What problems do you expect when generating and transferring 1000 relay keys? (besides the descriptor limit) ... but before trying to solve any problems it is probably best to answer the question whether a single entities should run >5% CW fraction at all. > There are about 7000 relays in > total, with over 1000 of them (almost 40% of the capacity) at only three > ASes. Top 3 ASes currently account for 32% cw fraction. https://compass.torproject.org/#?exit_filter=all_relays&links&sort=cw&sort_… but the top 1000 relays account for >72% cw fraction https://compass.torproject.org/#?exit_filter=all_relays&links&sort=cw&sort_…

7 18

TheOnionBox v2.1 released!
by Ralph Wetzel 20 Mar '16

20 Mar '16

1 0

Exitmap module to count CloudFlare CAPTCHAs
by Philipp Winter 20 Mar '16

20 Mar '16

I wrote an exitmap module [0] that can tell us how many exit relays see a CloudFlare CAPTCHA when connecting to a given site. First, I ran the module for coreos.com because it uses CloudFlare, but the owner configured it to whitelist Tor. Indeed, only one out of 864 exit relays saw a CAPTCHA: <https://atlas.torproject.org/#details/7DD29A65C370B86B5BE706EA3B1417745714C…> Next, I ran the module for cloudflare.com, which does not seem to whitelist Tor. 638 (75%) exit relays saw a CAPTCHA and 211 (25%) didn't. [0] <https://gitweb.torproject.org/user/phw/exitmap.git/tree/src/modules/cloudfl…> Cheers, Philipp

3 3

GoDaddy null-routing Tor Exit IPs
by Dhalgren Tor 20 Mar '16

20 Mar '16

FYI Tor-Relays GoDaddy AS26496 is null-routing selected Tor Exits, presumably in response to abuse originating from them. Know of two thus far FE67A1BA4EF1D13A617AEFB416CB9E44331B223A 2016/01/26 ashtrayhat3 A0F06C2FADF88D3A39AA3072B406F09D7095AC9E 2016/03/16 Dhalgren though probably more exist. Appears to affect faster relays. Affected relays running 'unbound' for DNS may experience total DNS request freeze and should switch to 'named' to mitigate the failure. Null-route seems to be manual and persist for indeterminate time. Null-routed IPs will not be able to ping or connect to address listed in the report at http://www.cidr-report.org/cgi-bin/as-report?v=4&as=AS26496 Information on how this was discovered can be found at #18580: exit relay fails with 'unbound' DNS resolver when lots of requests time-out https://trac.torproject.org/projects/tor/ticket/18580

1 0

please send me the hosters you use
by harvie josh 20 Mar '16

20 Mar '16

Hello! I'm spending quite some time in finding new cost-efficient VPS hoster in "unpopular" countries (non-exit). The relay community would actually have a lot information to provide in that regard - I think. I would really appreciate if you can share any hoster that provides VPSes with the following properties: * cost efficiency: at least 4 MBit/s per $ / month (min 20MBit/s) * not located in NL, FR, DE, US, GB, AS16276, Digital Ocean ASes * KVM or Xen based (no OpenVZ) * unmetered or at least 7TB/month outbound * proper https for customer area (reboot functionality, console access, ...) * English customer area You can also help by adding hoster information to your contactinfo field: ISP:<url to hoster> so others can find that (sometimes it isn't easy to find the hoster based on IP/AS information). So far I made good experience with itldc.com + price + reliable + SSH pub key pre-polulated in VPS + custom ISO possible + greate CPU performance in UA DC - plaintext root password in email mixed experience with seflow.it - almost regular outages - poor support (response time and know-how) - unable to provide correct billing information for hourly billed VPSes (start-stop times) ~ CPU performance + price (especially memory) + root password not disclosed via plaintext email unusable hoster ----------------------- alexhost.md Unreliable; to many outages serverastra.com no https coolhousing.net no https server.ua no https prohoster.info OVH reseller layeronline.com OVH reseller vmline.pl polish interface only unixhost.pro poor CPU/network performance (<15MBit/s) www.hosteasy.eu passport copy required ablenet.jp passport copy required albahost.net simply failed to provide working VPS vinahost.vn international traffic limited to 10MBit/s www.infiumhost.com no proper https (self-signed cert) alphavps.bg metered <1TB/month xserver.ua customer area language vps.ua customer area language Rx-name.ua no reaction to email request If you can not suggest specific hoster but good sites to find new hoster that is also great, like: https://www.exoticvps.com/ https://www.lowendtalk.com/ https://www.webhostingtalk.com -- harvie josh

5 7

What IPs does Torbrowser need?
by Martin Kepplinger 19 Mar '16

19 Mar '16

Hi Imagine a router that want to only whitelist the IP addresses that Torbrowser needs to work. What IPs would it need (for start up and browsing) ? * Guards * Authorities * HSDir flagged relays (?) and would such a whitelisting of IPs even work? At least I think DNS can be ignored as it is routed over Tor too. Any more thoughts? ps: please leave me in CC as I'm not on the tor-talk list. thanks!! martin

2 1