- tor-relays - lists.torproject.org

Two bridge relay questions
by Tor-Node.net 05 Aug '16

05 Aug '16

Hi! I run an obfs4 bridge. 1) Why is the advertised bandwidth 56.72 KB/s when the relay is on a (shared) gigabit connection? According to my experiments it should be several MB/s. 2) Where can I submit my bridges to help people in Iran, China etc, besides the Tor BridgeDB? Kind regards Tor-node.net

3 2

Exit relay funding
by Michael McConville 04 Aug '16

04 Aug '16

Hi, everyone. I'm an experienced Tor relay operator and a mostly dormant community member. My main relay these days is on a dedicated server running OpenBSD and moving 3-4 MB/s. It costs me $35/month. https://atlas.torproject.org/#details/CDAB3AE06A8C9C6BF817B3B0F1877A4B91465… Sadly, I have to shut it down at least temporarily if no one can help me pay for it. Is anyone interested? You can search the mailing lists to see that I've been contributing for a few years, and I can give more verification if you'd like. Thanks for your time, Michael McConville

23 40

Re: [tor-relays] tor-relays Digest, Vol 67, Issue 11
by Flipchan 04 Aug '16

04 Aug '16

Auto update with cron, audit it like a normal server tor-relays-request(a)lists.torproject.org skrev: (4 augusti 2016 14:00:07 CEST) >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. Re: experiences with debian tor 0.2.8.6 package from > deb.torproject.org (tor relay) > 2. Any security tips on running a TOR relay? (Andrew) > 3. Re: Exit relay funding (Petrusko) > 4. Re: experiences with debian tor 0.2.8.6 package from > deb.torproject.org (Peter Palfrader) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 4 Aug 2016 08:01:32 +0200 (CEST) >From: tor relay <torrelay3(a)mailbox.org> >To: tor-relays(a)lists.torproject.org >Subject: Re: [tor-relays] experiences with debian tor 0.2.8.6 package > from deb.torproject.org >Message-ID: <249633305.6901.1470290492290(a)office.mailbox.org> >Content-Type: text/plain; charset="utf-8" > >https://trac.torproject.org/projects/tor/ticket/19825 >

1 0

Tor relay on pfSense
by Edwin Garzón 04 Aug '16

04 Aug '16

Hello you have an updated tutorial for "Set Up Tor relay on pfSense 2.3.2" Thanks Edwin

1 0

Re: [tor-relays] is explicit DirPort needed anymore under Tor 0.2.8.6?
by Tristan 03 Aug '16

03 Aug '16

I'd like to peep in here and say that Orbot (Tor on Android) is still using version 2.7.5. Until someone updates the app to 2.8.6, those users will still need a DirPort.

1 0

Re: [tor-relays] tor-relays Digest, Vol 67, Issue 2
by Flipchan 01 Aug '16

01 Aug '16

What isp do u have in Sweden , i have had simular isp problems where i have got a letter in the mail (a real irl letter in paper^^). tor-relays-request(a)lists.torproject.org skrev: (1 augusti 2016 14:00:12 CEST) >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. Re: Got a visit from the police this morning.. (Marco A. Calamari) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 01 Aug 2016 11:45:32 +0200 >From: "Marco A. Calamari" <marcoc_maillist(a)marcoc.it> >To: tor-relays(a)lists.torproject.org >Subject: Re: [tor-relays] Got a visit from the police this morning.. >Message-ID: <1470044732.4836.6.camel(a)marcoc.it> >Content-Type: text/plain; charset="UTF-8" > >On Sun, 2016-07-31 at 14:54 +0100, Jonathan Baker-Bates wrote: >> I think this issue has been discussed here before. >> >> The general opinion on the list is that it's not a good idea to >> run an exit at home. It's probably not worth the hassle. > >For the peace of the mind and of the home sure. > >OTOH if all put exit nodes on external providers, > the vulnerability of the Tor network raise a lot, > hoping that no one run it on VM without knowing/caring > of this .... > >JM2C > >> On 31 July 2016 at 14:13, Stig Atle Steffensen <stigatle@cryptol >> ab.net> wrote: >> > I never thought I would be one of those operators who had to >> > deal with the police or anything like that. >> > I've done all I can to set things up so that it's easy to see >> > that I run a exit node. >> > >> > I have a disclaimer on my website : >> > https://stigatle.no/index.php/tor-exit-node/ >> > >> > and if you go to the ip of the node, you'll see the same info: >> > https://185.97.32.18/ >> > >> > I run this node - which is no secret: >> > https://atlas.torproject.org/#details/04250C3835019B26AA6764E8 >> > 5D836088BE441088 >> > >> > So, back to earlier this morning. >> > Suddenly got a hard knock on my door, I was surprised because >> > we never get visitors. >> > I saw it was the police (2 officers), and they asked if we >> > could talk in private, because >> > they heard my kids (2 and 4) and my wife upstairs, I said yes, >> > no problem, let them in. >> > >> > They would not let me know what it was about at first, they >> > asked a lot about what I did yesterday, >> > easy for me to answer since I was out climbing mountains all >> > day long. >> > Then asked a lot about who has access to my connection at >> > home, It's just me, my wife, no one else. >> > >> > Then I start to ask a bit, and I thought about the exit node I >> > run, I quickly confirmed >> > that it was the exit node (which is in sweden and not in >> > Norway where I live) that was the reason why they where at my >> > house. >> > All though - 2 second check would confirm to them that the >> > server is not at my house, and the impression they gave me >> > until I >> > showed the Exit node was that they thought it was sent from my >> > house. >> > >> > I have blocked the email ports on the exit node, but the issue >> > was that a email had been sent through hotmail (web), >> > threatening Angela Merkel, that's why they where at my house >> > this morning. >> > >> > >> > I got the chance to explain everything as best I could, >> > explained how it all worked, and why >> > I run a exit node, and I feel they got all the answers they >> > needed. They then left - and for now that was that. >> > >> > I would be put on some kind of list, but that list would also >> > explain that I operate a tor exit node. >> > I'm happy with that, and hopefully this will be all that >> > there's to it. >> > >> > I might have to do some more explaining if I travel to >> > sweden\germany, but that's fine with me. >> > >> > >> > Anyone else here that has this happen to you recently as >> > well?.. >> > >> > >> > _______________________________________________ >> > tor-relays mailing list >> > tor-relays(a)lists.torproject.org >> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-rela >> > ys >> > >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >tor-relays mailing list >tor-relays(a)lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > >------------------------------ > >End of tor-relays Digest, Vol 67, Issue 2 >***************************************** -- Sincerly Flipchan

1 0

outgooing UDP flooding on middle relay
by pa011 01 Aug '16

01 Aug '16

Hello, one of my middle relays got auto limited by the ISP because of "outgooing UDP flooding ". The VPS is pure debian8, fail2ban, pub key and nothing else installed - so I highly doubt the give reason for the traffic limitation. Also I cant find anything in the log files. Anybody having experience with such an issue? What to check for please? Paul

5 12

Don't use Google's DNS server
by Philipp Winter 29 Jul '16

29 Jul '16

I created a new diagram that illustrates the popularity of DNS resolvers used by exit relays. The diagram shows nine autonomous systems that hosted the most popular resolvers at some point over the last months. These autonomous systems are owned by Google, INIT7, LeaseWeb, Visual Online, OVH, OpenDNS, NForce Entertainment, Cyberdyne, and Level3. The x axis shows time and the y axis shows the fraction of DNS requests that the respective AS can observe: <https://nymity.ch/dns-traffic-correlation/img/exit-resolvers-2015-05.png> The two most popular setups are Google's 8.8.8.8 and local resolvers, i.e., exit relays doing their own resolution. Occasionally, Google got to see more than 40% of all DNS requests exiting the Tor network. That is concerning, particularly given Google's role in the PRISM program. No other autonomous system is getting even close. Please refrain from using 8.8.8.8. Instead, set up your own resolver, or at least use the one provided by your ISP. Here's Peter's quick guide on how to set up your own resolvers [1]: On Thu, Jan 08, 2015 at 04:11:09PM +0100, Peter Palfrader wrote: > o apt-get install unbound > o remove all nameserver entries in /etc/resolv.conf and add one for the > local recursor. Either manually or use (untested): > sed -i -e 's/^nameserver /#&/; $a nameserver 127.0.0.1' /etc/resolv.conf > o prevent anything else from modifying that file ever again: > chattr +i /etc/resolv.conf Note that running your own resolver is not universally safer because the exposure of DNS requests to network adversaries is greater. It's a tricky trade-off that we are currently trying to understand better [2], but increased exposure to network-level adversaries seems less bad than having Google see almost half of all DNS requests. If you are wondering how I created the above diagram, have a look at the measurement method [3]. [1] <https://lists.torproject.org/pipermail/tor-relays/2015-January/006147.html> [2] <https://nymity.ch/dns-traffic-correlation/> [3] <https://lists.torproject.org/pipermail/metrics-team/2016-February/000078.ht…> Cheers, Philipp

10 15

Re: [tor-relays] cheap unmetered non-exit VPS offers
by Tor-Node.net 28 Jul '16

28 Jul '16

Markus Koch <niftybunny(a)googlemail.com> wrote: > exit allowed? I can vouch for www.stayon.no VPS with dedicated, unmetered 1 Gbps connection. 1 GB RAM / 1 CPU @ 2.6 GHz Price: 149 NOK/month (~ 16 EUR / 17 USD). Tor exit friendly. Their abuse departement will ask you to block destination IPs if it's something serious. Kind regards Tor-node.net

2 1

AWS abuse handling
by Snehan Kekre 28 Jul '16

28 Jul '16

Hi All, I have a *free* membership for a year on Amazon's AWS (*capped* at 15GB/month of traffic each way). I've been running an exit node with a reduced exit policy on an ec2 instance for months and have received my first abuse notice. I'm sure a few on this mailing list may have received the same or similar abuse notification from Amazon. Besides shutting down the exit, what measures did you take to deal with this? What would be the consequences of ignoring their email and continuing to run it? Note: I'm a student and am running on a really tight budget at the moment (reason for not hosting it on a paid vps) Any suggestion(s)/help is appreciated :) Best, Snehan ----------------------------------------------- The contents of the Abuse notice: Hello, We've received a report(s) that your EC2 instance(s) Instance Id: IP Address: has been has been operating as a TOR Exit node. Operating a TOR Exit node is forbidden in the AWS Acceptable Use Policy (hxxps://aws.amazon.com/aup/) We've included the original report below for your review. Please take action to stop the reported activity and reply directly to this email with details of the corrective actions you have taken. If you do not consider the activity described in these reports to be abusive, please reply to this email with details of your use case. If you're unaware of this activity, it's possible that your environment has been compromised by an external attacker, or a vulnerability is allowing your machine to be used in a way that it was not intended. We are unable to assist you with troubleshooting or technical inquiries. However, for guidance on securing your instance, we recommend reviewing the following resources: * Amazon EC2 Security Groups User Guide: hxxps://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.… (Linux) hxxps://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/using-network-securi… (Windows) * Tips for Securing EC2 Instances: hxxps://aws.amazon.com/articles/1233 (Linux) hxxps://aws.amazon.com/articles/1767 (Windows) * AWS Security Best Practices: hxxp://media.amazonwebservices.com/AWS_Security_Best_Practices.pdf If you require further assistance with this matter, you can take advantage of our developer forums: hxxps://forums.aws.amazon.com/index.jspa Or, if you are subscribed to a Premium Support package, you may reach out for one-on-one assistance here: hxxps://console.aws.amazon.com/support/home#/case/create?issueType=technical Please remember that you are responsible for ensuring that your instances and all applications are properly secured. If you require any further information to assist you in identifying or rectifying this issue, please let us know in a direct reply to this message. Regards, AWS Abuse " ---------------------------------------------------------------------------

9 21