May 2020 - tor-relays - lists.torproject.org

May 29th - Run and use Tor Bridges to bypass censorship and surveillance! (Online)
by gus 27 May '20

27 May '20

Hi, on May 29th 2020, members of The Tor Project will be online to support and explain how to help users in countries that censor the Internet. From 1200 UTC to 2000 UTC, we will teach you how to run a Tor bridge and answer questions about our anti-censorship technology. This event is public and open for everyone! The event will happen via text (not video or audio) on IRC, in the channel #tor-relays on irc.oftc.net. Learn here how to connect to our IRC: https://support.torproject.org/get-in-touch/ More info: https://blog.torproject.org/run-and-use-tor-bridges-irc-meetup ## About bridges Bridges are useful for Tor users living in oppressive regimes, and for people who want an extra layer of security because they're worried somebody will recognize that they are contacting a public Tor relay IP address. A bridge is basically a private Tor relay that helps you hide the fact that you are using the Tor network. To set up a bridge, take a look at the instructions in our Community portal: https://community.torproject.org/relay/setup/bridge/ ## About this event This is our first online event promoting bridges and anti-censorship technology and you can join at any time between 1200 UTC and 2000 UTC. Several members of The Tor Project will be around to answer questions and provide technical support related to bridges and anti-censorship technology. We expect to answer your questions and teach attendees how they can help friends in censored countries, how they can set up Tor bridges, and what else they can do to fight online censorship. ## Learn more - Tor Browser User Manual https://tb-manual.torproject.org/bridges/ https://tb-manual.torproject.org/circumvention/ - Censorship section on Support portal https://support.torproject.org/censorship/ - Community portal - Relay Operators section https://community.torproject.org/relay/ - Snowflake https://snowflake.torproject.org/ -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/

1 0

Bridge log indicates missing geoipdb
by nottryingtobelame＠protonmail.com 26 May '20

26 May '20

>If you use Raspbian, that's still a 32-bit OS Insert shocked Pikachu meme. I guess I had to learn that some how, but I have to beat myself up a little for not catching that sooner. I will upgrade. Thank you.

1 0

Bridge log indicates missing geoipdb
by nottryingtobelame＠protonmail.com 26 May '20

26 May '20

Thank you for the reply. I have one on a Raspberry Pi 3B+ and one on a Raspberry Pi 4. I believe both are 64-bit ARM.

2 1

Weird Issue With nyx
by AceOfRelays32 26 May '20

26 May '20

Chowning the torrc file fixed it, and I tried adding myself to the Tor group but that doesn't exist for whatever reason. However chowning the torrc file and then rebooting caused Tor to give my relay a new fingerprint which is slightly annoying. New relay though so I'm not too bothered by it. Thanks! -AceOfRelays32-

1 0

Why is this Middle Relay almost unused ?
by petrarca＠protonmail.ch 26 May '20

26 May '20

I'm wondering why this relay is almost unused: Fingerprint 605EE4375EE4C38215C8949F5808863749FD4F4A ? It's running on a 1 Gbit link and there is plenty of unused bandwidth. The bandwidth is set to 42 Mbps (even prioritized on the internet link). There were no outages for months and the connection is stable and fast. There's also plenty of resources available on the actual router (tor instance). Relay monitoring shows usage average around 0.5 - 1 Mbps only (so around 1-2 percent of the available bandwidth). Consensus Weight is down to only 99. Any idea what could be the reason of the low usage, low Consensus Weight ?

1 0

Weird Issue With nyx
by AceOfRelays32 26 May '20

26 May '20

It would seem my relay is fully functional. Being it has only been up for less than 3 hours though I can't 100% confirm that. Anyways, when I launch nyx to check it's status, I get a permission error from /run/tor/control.authcookie. Chowning /run/tor/control.authcookie and then running nyx solves that issue, however it doesn't persist on reboots. Running nyx as root also fixes it. I wrote an alias to automate chowning and running nyx for the time being, but I'm wondering if there is a better fix.

2 1

Bridge log indicates missing geoipdb
by nottryingtobelame＠protonmail.com 26 May '20

26 May '20

Had the following log entries for my bridge: May 25 11:49:50.000 [warn] Failed to open GEOIP file /usr/share/tor/geoip. May 25 11:49:50.000 [warn] We've been configured to see which countries can access us as a bridge, and we need GEOIP information to tell which countries clients are in. Tried to run sudo apt install tor-geoipdb and got this: The following packages have unmet dependencies: tor-geoipdb : Depends: tor (>= 0.4.3.5-1~d10.buster+1) but 0.4.2.7-1~d10.buster+1 is to be installed E: Unable to correct problems, you have held broken packages. I saw on tor-announce that 0.4.3.5 is out, but it looks like the buster package isn't available yet. I made sure I have the tor repo's in /etc/apt/sources.list and I have the proper signatures as everything validates when I run apt update. Is there a way to resolve this?

2 1

Tor Relay Web Ports
by mnlph74 25 May '20

25 May '20

Hi, I'm running a non-exit relay for quite some time now and I would like to open ports 53, 80, 443 (web ports) to be more useful. How do you handle fraudulent complaints? What is the best approach to this situation? Thank you for your help. Sent with ProtonMail Secure Email.

3 8

Re: [tor-relays] Why does it take 4 days to get the HSDir flag back?
by Roger Dingledine 23 May '20

23 May '20

On Thu, May 21, 2020 at 08:03:03PM +0200, tschador(a)posteo.de wrote: > after an update of tor it always take about 4 days to get the HSDir flag > back while the other flags are set very qick. What is the reason for > this delay? It's because the directory authorities are configured to wait that long before assigning the flag. See the MinUptimeHidServDirectoryV2 option: https://gitweb.torproject.org/tor.git/tree/src/feature/dirauth/dirauth_opti… It used to be 25 hours, long ago, with the reasoning that if a relay hasn't been up for a day, then it's too likely to go away again soon, and this churn causes reliability problems in reaching onion services. We changed it to 96 hours in late 2014, when we saw a Sybil attack (many new relays suddenly appearing) and realized that while they wouldn't become Guards for a while, they would become HSDirs quite quickly, and maybe we want to give ourselves a few more days after new relays appear before they get to become HSDirs. And here are two tickets on doing even more to make it hard for jerks to sign up relays with the goal of cheaply getting the HSDir flag: https://bugs.torproject.org/16538 and https://bugs.torproject.org/19162 And of course the long term fix is to drop the deprecated v2 onion service design, since the v3 onion service design is much better at limiting what an HSDir relay can learn about onion services: https://www.youtube.com/watch?v=Di7qAVidy1Y Hope this helps, --Roger

2 1

Re: [tor-relays] How do I add relays to a "family" and what are the benefits?
by Keifer Bly 23 May '20

23 May '20

1 0