tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Is it wise to continue to allow yahoo email accounts to request bridges?
by Keifer Bly 24 Mar '20

24 Mar '20

Hi all, So for those who did not know, Yahoo (and as such Yahoo Mail) is now owned by Verizon. They bought both Yahoo and AOL and combined them into Verizon Media. For this reason, it seems like allowing Yahoo Mail accounts would in turn allow a large scale ISP (in this case Verizon) to easily obtain bridges. Does anyone agree on this? It's just a thought. Thanks. --Keifer

2 1

Re: [tor-relays] Stable flag not appearing on my bridge.
by Keifer Bly 24 Mar '20

24 Mar '20

2 2

Relay Or/Dirport Unreachable
by Kathi 23 Mar '20

23 Mar '20

Plan: Configure relay on local cable connection (Century Link). The idea is to have the relay proofed operational the way I want it and then move it (torrc) to a droplet after it has been in operation for three days. Doing this saves cost in downloading to the droplet. Modem Zyxel C3000 _was_ set to port forward on 9001, 9030, and 9050 IP 192.XXX.X.X Turn off UpnP (plug and play) <relay fails with it on> GUFW is set to allow the above ports – reload to allow changes after much struggling/research to open ports 9001/9030 nc -zv 127.0.0.1 9001/9030 Connection to 127.0.0.1 9001 port [tcp/*] succeeded! <9030 also> Alrighty then! Tor –verify-config <many probs here, but cleared> No complaints NOTE: I know tor.Nyx should not be run as root, I get that. Tor/Nyx are running as root. I don’t know how to use debian-tor as usr. Nyx shows in it’s configuration as usr debian-tor. Su debian-tor produces a rollover back to root usr prompt. service tor start Nyx – No complaints, running as default. After just two minutes of operation the relay was running at 2 MB/s with bursts up to 3 MB/s. After the obligatory/frustrating twenty minute wait for or/dirport hand shaking I get:orport/dirport unreachable…. Adnauseum! Changed IP address to one given by tor, still unreachable. Lastly, I removed the 900l/9030 ports from the modem and installed 6969 as the orport. Changed GUFW, verified the changes took place, changed ip to real world IP 63.xxx.xxx.xxx in torrc. Hand shaking to the orport was almost immediate. Right now, the relay after twenty hours of operation is tortusing along at 20 B/s. Which to me is pure BS. Can someone give me some idea’s as to what I am doing wrong? Kathi

7 10

When will my relay gain the stable flag again?
by nottryingtobelame＠protonmail.com 19 Mar '20

19 Mar '20

My relay (903CA67D0DEB74CFBB01432840A26CB8C6C18FDF) is ~2 years old. Recently, I had a series of network issues that took my relay offline for unexpectedly long times. When it has gone offline before and lost the stable flag, it usually took only a couple days to pick it back up again. It is approaching 8 days since I finally got things resolved with a new router, but still no stable flag. I also used to have the guard flag, but I know I can't get back to guard status without the stable flag. Thanks.

2 1

When will my relay gain the stable flag again?
by nottryingtobelame＠protonmail.com 19 Mar '20

19 Mar '20

Disregard - the relay picked up the stable flag tonight.

1 0

Re: [tor-relays] Migrating to a new data center
by Isaac Grover, Aileron I.T. 18 Mar '20

18 Mar '20

Niftybunny, Thank you for the fun pictures. But the question on my mind: is "niftybunny" the brown marbled bunny or the larger white bunny? Or is "niftybunny" a cloud entity like the Borg?

2 1

Re: [tor-relays] Improving Relay IPv6 - RIPE Grant
by ILikeTor 18 Mar '20

18 Mar '20

Hi, I was wondering how you will implement IPv6-only relays. What limits will you set on how many relays can be per /(something)? Will you allow only two relays per /64, for example? Do you have any plans for that already?

3 2

Migrating to a new data center
by niftybunny 18 Mar '20

18 Mar '20

Comrades! Today the united rodent liberation army transitioned to a new data center in order to more effectively fight for privacy, security and freedom for every fluffy creature on this earth! We will work paw-in-paw to create a brighter future not only for us, but for every privacy-minded critter everywhere. Together we hop and together we fight! We are now online with 60cores/120 threads (Xeon), 384 gigabyte ram and a 60 gigabit connection. We will boost our puny traffic in the next weeks. For full transparency we also release these pictures of me and our QA team working hard to bring only the best of the best to you: https://i.imgur.com/iKh61E8.jpg <https://i.imgur.com/iKh61E8.jpg> https://i.imgur.com/4gnzncD.jpg <https://i.imgur.com/4gnzncD.jpg> https://i.imgur.com/DD0uaGC.jpg <https://i.imgur.com/DD0uaGC.jpg> https://i.imgur.com/VG7pm3S.jpg <https://i.imgur.com/VG7pm3S.jpg> https://i.imgur.com/wgRv8FU.jpg <https://i.imgur.com/wgRv8FU.jpg> niftybunny

4 5

Port Forwarding Question
by William Pate 17 Mar '20

17 Mar '20

This constantly trips me up. In my modem settings, I'm offered these options for port forwarding. I know I need to open 9001, but what do I enter into the external port fields? Thank you! William Pate willpate(a)pm.me 512-947-3311 inadequate.net

4 5

Fwd: Upcoming Tor security releases to fix a denial-of-service issue
by Nick Mathewson 16 Mar '20

16 Mar '20

---------- Forwarded message --------- From: Nick Mathewson <nickm(a)torproject.org> Date: Mon, Mar 16, 2020 at 1:25 PM Subject: Upcoming Tor security releases to fix a denial-of-service issue To: <tor-talk(a)lists.torproject.org> Hello! Some time this week, we currently plan to put out a set of security updates for all supported versions of Tor. These releases will fix a pair of denial-of-service bugs: one that we are classifying at "low" severity, and one that we are classifying at "high" severity. Our recommendation will be for everybody, including relays and clients, to upgrade once packages are available for their platforms. Although these vulnerabilities are "only" denial-of-service issues, any denial-of-service attack against Tor could be leveraged by an attacker to aid in a traffic analysis attack. To the best of our knowledge, these vulnerabilities are not being exploited in the wild. Currently supported release series are 0.3.5, 0.4.1, 0.4.2, and 0.4.3 (alpha). If you have not yet upgraded to one of those, the time to do so is soon. For our policy and process for handing security issues, please see: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/Securit… best wishes, -- Nick

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays