tor-relays May 2017

tor-relays@lists.torproject.org

57 participants
39 discussions

Bridge not being used
by Joel Cretan 19 May '17

19 May '17

Hi relay operators, I've run a number of relays, so I'm familiar with how this usually works for non-bridges. I'm working on a project that might want to connect through a bridge, so I thought I'd fire one of those up to offset the demands I'd be placing on the network. I've been operating this bridge for about 30 days with RelayBandwidthRate set at 5000 KBytes, which I thought might be attractive to some clients, since most bridges are so small. But checking my logs for the last few days, I don't seem to have had any clients at all recently. Is this expected for a bridge, as clients don't rotate their bridge very often, or is something possibly wrong? As far as I can tell, everything is working OK, because I can connect through it with my own Tor client. The server descriptor is published. I'll avoid pasting the whole torrc since it's a bridge, but I can do that with some parts removed if that would help. Thanks! jc

2 2

Re: [tor-relays] seized relays reported for blacklisting?
by nusenu 19 May '17

19 May '17

Hi Nicolas, thanks for your fast response. Nicolas Simond: > I'll do but I don't know if this has been done since I haven't received > any response. Ok so you tried to contact them already? (what email / channel did you use?) > But all relay have disapeared from the atlas. Are you saying that more than one of your relays was seized? I found the following relays (down) with your contactinfo, did all 3 get seized? +----------+-----------------+---------------------+ | FP | nickname | last_seen | +----------+-----------------+---------------------+ | 96D67782 | darkstar | 2017-05-17 09:00:00 | | 6B356C10 | dustofnightmare | 2017-05-17 09:00:00 | | C46A33E7 | InFlames | 2017-05-13 16:00:00 | +----------+-----------------+---------------------+ Atlas is currently hardly working since its backend (onionoo.torproject.org apparently has some availability issues). Atlas also only shows relays that have been running at some point within the last 7 days (which should not be a problem in this case). -- https://mastodon.social/@nusenu https://twitter.com/nusenu_

1 0

DirCache 0
by Paul 19 May '17

19 May '17

Running a relay on small RAM I putted "DirCache 0" to save memory. As one can read here https://www.torproject.org/docs/tor-manual.html.en "Setting either DirPort or BridgeRelay and setting DirCache to 0 is not supported. (Default: 1) " I cant set a DirPort as well, which means I cant publish a DirPortFrontPage Exit-notice. Any idea how to circumvent this problem. Thanks Paul

2 1

Strange behaviour Tor 0.2.9.10 - off topic
by Felix 18 May '17

18 May '17

Hi everybody I walked through the March postings and found: > (Please don't put -- in your emails. Some people use broken > mail readers that hide everything below a -- .) Indeed it's not broken, it's *Usenet Signature Convention* https://tools.ietf.org/rfc/rfc3676.txt (chapter 4.3.) That's old school - how we saved bandwidth in ancient times :) -- Cheers, Felix

2 1

TROVE-2017-002: deb.torproject.org 0.3.0.x repos no longer updated? - help yourself
by Felix 18 May '17

18 May '17

Hi If you suffer from: (and https://www.freshports.org/security/tor/ is still on 3.0.6) > To help the 1.3% cw-fraction / 87 FreeBSD relays I filed > a ticket here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219364 and you are on FreeBSD source you upgrade to 3.0.6 and then put a small hack in place: Go to ports security/tor and edit the 3.0.6 distinfo to: SHA256 (tor-0.3.0.7.tar.gz) = 9640c4448ef3cad7237c68ed6984e705db8fb2b9d6bb74c8815d01bb06527d02 SIZE (tor-0.3.0.7.tar.gz) = 5779422 Change the 3.0.6 Makefile to: PORTVERSION= 0.3.0.7 Copy tor-0.3.0.7.tar.gz from https://dist.torproject.org/ to /var/ports/distfiles/ # cd /usr/ports/security/tor && make deinstall clean # cd /usr/ports/security/tor && make install And voila 3.0.7 shows up. Works as well for jails (/usr/jails/myjail/var/ports/distfiles/). If you come from some older versions please check ports/UPDATING, libevent is 2.1.8 now. -- Cheers, Felix

1 0

Re: [tor-relays] Strange behaviour Tor 0.2.9.10
by Geoff Down 18 May '17

18 May '17

Further information. Curl error Failed to receive SOCKS5 connect request ack. and from earlier, Tor log Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection to [scrubbed]:80. Giving up. -- http://www.fastmail.com - A no graphics, no pop-ups email service

3 12

Bandwidth settings
by Torix 17 May '17

17 May '17

This is a newbie question, but I'm not sure where else to ask it. I had an older desktop box from a decade ago, so I put Debian tor on it as per the directions and set it up as a middle node (exit policy to reject *:*) at home. I added arm and vnstat to be able to look at it. I've never done anything with tor before, so I know nothing but what I've read in the past 2 weeks. My question is about bandwidth. I made a mistake at first with Kbytes and kbits, but currently have it set at 200KBytes steady, 300KBytes burst. This translates in the default arm display to 1.5Mb/s and 2.3Mb/s. I use Verizon Fios. When I did a speed test from Verizon, I got 60 Mbps up and 70 Mpbs down. I currently have not set any accounting max daily limit. It seems to me that I could add 10 times the bandwidth and still be at 15/23 Mbps out of 60-70 Mpbs, or only a quarter of my total bandwidth. Were I to do this, 1. would we notice at home, where we don't stream video; just run browsers and remote desktop about 8 miles away to work. 2. or would Verizon notice first the bandwidth or the amount of data going through our connection? Which would be the first limit? Bandwidth or data? In terms of data, I've already run 11.5 GB through tor yesterday, out of about a 17GB theoretical maximum at these bandwidth settings. Would 170GB/day be outrageous to Verizon if I cranked the bandwidth up? Would we notice it? Hoping someone might be able to add to my vast experience of 3 days up. Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 4

Fallback Directory Update: May 2017
by teor 17 May '17

17 May '17

Dear Relay Operators, We have rebuilt the list of fallback directory mirrors in Tor[0] for the upcoming 0.3.1 release. The new list will also be backported to Tor 0.2.8 and later. If you're asking: Q: What's a fallback directory mirror? See [1]. Q: Is my relay on the list? Search [2] for your relay fingerprint or IP address and port. (I used to BCC this email to all operators on the list, but that's a lot of work!) Q: What do I need to do if my relay is on the list? Keep the same IP address, keys, and ports. Email me or this list if the relay's details change. Q: Can my relay be on the list next time? We need fast relays that will be on the same IP address and port for 2 years. Email me to get on the potential relay list[3], or to update the details of your relay. Every release or two we run a script to choose about 150-200 relays for the list. Q: Why didn't my relay get on the list this time? We check a relay's uptime, flags, and speed[4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time. It's good to have some new relays on the list every release. That helps tor clients, because blocking the whole list is harder. Tim [0]: https://gitweb.torproject.org/tor.git/commit/src/or/fallback_dirs.inc?id=5b… [1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_… T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------

1 0

WannaCry fallout FYI
by Jon Gardner 16 May '17

16 May '17

From the SNORT folks... http://blog.talosintelligence.com/2017/05/wannacry.html?m=1 ".... Additionally, organizations should strongly consider blocking connections to TOR nodes and TOR traffic on network. Known TOR exit nodes are listed within the Security Intelligence feed of ASA Firepower devices. Enabling this to be blacklisted will prevent outbound communications to TOR networks." <>< Jon L. Gardner Mobile: +1 979-574-1189 Email/Skype/Jabber: jon(a)brazoslink.net AIM/iChat/MSN: jlg(a)mac.com

8 14

Tor and ufw
by je suis 15 May '17

15 May '17

Hello everyone One of my friends got a ransomware and, even if I am on Linux and I take care when browsing, with such a proof beside me I thought I'd secure myself a bit, so I got ufw. I am running a middle relay, and so far it went just fine with ~2.5MB bandwidth, even if only in the daytime, morning to evening (laptop...; I do plan in getting a RaspberyPi in the future). I followed this page for setting up ufw with tor: https://help.ubuntu.com/community/TorDedicatedUser , even if I have Archlinux. I didn't use all in there, only the part right below "Traffic redirection", with ufw in the command line. Now, if I see the relay with 25kB, it's a miracle. So, obviously, I did something wrong. Is there a page with proper explanations for dummies like me? If it helps, my net comes from a router that handles cable TV and phone, as well. Vlad

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays May 2017