Hi,
IMHO, this is not a good idea. Tor relay IPs are public, so they are likely to
be blocked as part of censorship in some countries. This will greatly reduce
the usefulness of the bridge running on the same IP. Running both at the same
time on the same public IP does not add much value.
If y
Hi everybody
Just to let you know.
Yesterday between 21:26 and 21:31 utc the relay
03C3069E814E296EB18776EB61B1ECB754ED89FE (Tor 0.4.7.4-alpha, LibreSSL
3.4.2) received a connection burst of 2k+ source addresses out of 174
/8 ip4 nets (1-223/8).
They were kicked off by the packetfilter because t
On 3/20/22 17:14, Felix wrote:
They were kicked off by the packetfilter
IMO it is a bad idea to filter Tor traffic.
--
Toralf
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Georg Koppen:
Hello!
It's time again to get relays upgraded running an EOL Tor series
(0.3.5.x). We'll start reaching out to operators with valid contact
information this week and plan to start reject relays which are still on
0.3.5.x about 4 weeks from now on at the begin of March. You can f
Hello,
TL;RD:
if you are a bridge operator please update obfs4proxy to a version>=0.0.12.
There is a new version of obfs4proxy (>=0.0.12) which fixes a security
issue[0].
Tor Browser has already updated to the new version, which reduces a bit the
security problem, but introduces a partial i
