tor-relays October 2019

tor-relays@lists.torproject.org

45 participants
35 discussions

Question
by Rubles 30 Oct '19

30 Oct '19

I tried running a bridge but my systemLog said: Please upgrade! This version of Tor (0.3.2.10) is not recommended, according to the directory authorities. Recommended versions are: 0.2.9.15,0.2.9.16,0.2.9.17,0.3.5.8,0.4.0.5,0.4.0.6,0.4.1.2-alpha,0.4.1.3-alpha,0.4.1.4-rc,0.4.1.5,0.4.1.6,0.4.1.7,0.4.2.1-alpha,0.4.2.2-alpha,0.4.2.3-alpha (I used sudo apt-get install tor - on Mint) so I checked out https://support.torproject.org/apt/tor-deb-repo/ and when I tried gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - it didn't work as it said gpg: WARNING: unsafe ownership on homedir gpg: [stdout]: write error: Broken pipe gpg: build_packet(2) failed: Broken pipe gpg: key export failed: Broken pipe Here are some other things it said: Looks like client functionality is working. Bootstrapped 100%: Done Your server has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. What do I do?

2 1

36C3 voucher
by Niels Hesse 28 Oct '19

28 Oct '19

Anybody holding a Voucher for 34C3 in Leipzig at the end of December? https://tickets.events.ccc.de/36c3/docs/ <https://tickets.events.ccc.de/34c3/docs/>? While still running several Exits I would be more than happy to meet others there Thanks

2 1

Tor can exceed your AccountingMax in 0.4.0+
by Roger Dingledine 24 Oct '19

24 Oct '19

Hello wonderful relay operators, I wanted to let you know about a bug that might affect you if you use the AccountingMax option, in Tor 0.4.0 and later. Here's the ChangeLog entry from the upcoming 0.4.2.3-alpha: o Major bugfixes (relay): - Relays now respect their AccountingMax bandwidth again. When relays entered "soft" hibernation (which typically starts when we've hit 90% of our AccountingMax), we had stopped checking whether we should enter hard hibernation. Soft hibernation refuses new connections and new circuits, but the existing circuits can continue, meaning that relays could have exceeded their configured AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha. That is, when your relay enters "soft" hibernation, you stop accepting new connections and new circuits (good), but you stop checking whether you've hit the hard limit and need to close down the remaining circuits (bad). The bug has the additional impact that when your Tor has entered soft hibernation, it stops updating the 'state' file in its DataDirectory, which means it doesn't record new bytes spent in the interval after that point. You can read more details on the trac ticket: https://bugs.torproject.org/32108 We'll have an 0.4.2.3-alpha release out soon with what we hope is a fix. And if it looks good then we'll plan to put out new 0.4.0.6 and 0.4.1.7 stables. In the meantime, if this bug affects you, you might do some combination of the following: * Watch your relay's bandwidth use and logs more carefully than usual * Downgrade to Tor 0.3.5.8 until the newer stables are ready * Set your RelayBandwidthRate to a lower value so you don't hit soft hibernation as quickly during this interval * Apply the two-line patch yourself (and let us know whether anything breaks) Sorry for the troubles, --Roger

1 0

public open socks port
by ylms 23 Oct '19

23 Oct '19

Hello all, I am wondering if there is any reason why one should not open the socks port of Tor to the public internet? I mean I run a Tor exit or relay, so why should I not open the port and give it to people that can't install Tor on some devices? Thanks for your thoughts. yl

4 3

Tor Relay on Pi Up
by William Pate 22 Oct '19

22 Oct '19

Put one up on my Raspberry Pi using the directions at https://community.torproject.org/relay/setup/bridge/debian-ubuntu/: https://metrics.torproject.org/rs.html#details/F38EE238CCB90EE18EC63361CB45… William Pate willpate(a)pm.me 512-947-3311 inadequate.net

1 0

Shit happens
by lists＠for-privacy.net 22 Oct '19

22 Oct '19

Ohh fuck. Too many terminals open and in the wrong: "rm -R / var / lib / tor-instances" I idiot of course have _no_ backup of the keys. :-( -- ╰_╯ Ciao Marco! My family:6D6EC2A2E2ED8BFF2D4834F8D669D82FC2A9FA8D

1 0

Operator straw poll: Reasons why you use Tor LTS versions?
by Mike Perry 21 Oct '19

21 Oct '19

Hello relay operators, Thanks for running relays, and thanks to those of you who are moving off of our old EOL Tor versions. Thanks especially to those of you who moved directly to Tor 0.4.1! We would like to transition the LTS Tor to be for use in edge/client/non-relay infrastructure only. We would like to minimize even that use. We need to update our network protocols to improve performance, security, and to add defenses against DoS attacks. Doing this while supporting LTS for relays is expensive, especially when large backports must be done to keep the network safe. It also slows down the uniform deployment of performance improvements, which contributes to the frustrating user experience of abysmal-but-rare performance edge cases. Unfortunately, we still have something like 2500 relays on either Tor 0.2.9-LTS or Tor 0.3.5-LTS. What are the reasons for this? My guess is the top 5 most common responses are: 1. "I didn't know that Debian's backports repo has latest-stable Tor!" 2. "I didn't see the Tor Project repos mentioned in Tor's Relay docs!" 3. "I'm running a distribution that Tor Project doesn't have repos for." 4. "I rolled my own custom Tor from git and forgot about it." 5. "My relay machine was not getting any updates at all. Oops." Does anyone have a reason that they think many other relay operators also share? How can we fix that for you, or at least, how can we make it easier to run the very latest stable series Tor on your relay? -- Mike Perry

10 17

Install on Tor on fresh Debian 10 failed (gpg key invalid)
by Olaf Grimm 20 Oct '19

20 Oct '19

Hello! I updated my VPS with a fresh Debian 10 install. According procedure in the documentation 'curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E8… | gpg --import' I get the error message '2019-10-17 20:34:32 (1.01 MB/s) - ‘A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc’ saved [19665/19665] gpg: no valid OpenPGP data found. gpg: Total number processed: 0 What is going wrong? Is this an invalid key? After weeks ago my other install on Debian 10 was ok. Best regards! Olaf

4 5

DDNS with Relays and/or Bridges?
by nottryingtobelame＠protonmail.com 20 Oct '19

20 Oct '19

Forgive me if this is a dumb or newbie question, but can DDNS be used with either relays or bridges? I was considering setting up DDNS with FreeDNS mostly for my bridge so that if the IP changes (I have chosen not to subscribe to a static IP with my ISP), my clients can still access the bridge, rather than having to reset and start the bridge from scratch. Obviously I would not make it "torbridge.anonymousnetwork.com" or anything that would suggest its true use. Maybe something like "photoserver.whatever.com" or something like that. If DDNS can be used, my follow-up question is where all would I need to set that information? I'm guessing just in torrc? I do not remember the flag for identifying your IP, as I've always left it blank for Tor to guess, but could the DDNS hostname be entered here in lieu of the IP? Thanks for your time.

3 2

Using unattended upgrades with tor expert bundle
by Keifer Bly 19 Oct '19

19 Oct '19

Hi all, So I have been running an OBFS4 bridge via the Tor Expert Bundle for a year now, and it is going quite well. However, from what I have researched, using unattended upgrades to keep tor up to date is configured in the torrc file. I am wondering, can this be configured in tor expert bundle? Thanks very much. --Keifer

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays October 2019