Re: [tor-relays] From [tor-announce] Tor stable release 0.4.7.8 - Security Fix

2022-06-20 Thread Spydar007 via tor-relays
Hello,

This was an issue back on June 18 when you got that log message, but 0.4.7.8 is 
recommended in the consensus now (you'll see on Relay Search that the relays 
don't have the "experimental" or "not recommended" flags).

Cheers
On 20 Jun 2022 at 11:47 +0100, Felix , wrote:
>
> > We have released tor 0.4.7.8 earlier today, a new stable version for
> > the 0.4.7.x series containing an important High severity security
> > fix. The affected tor are only those of the 0.4.7.x series as in from
> > tor-0.4.7.1-alpha to tor-0.4.7.7.
>
> Jun 18 10:08:46.000 [notice] This version of Tor (0.4.7.8) is newer
> than any recommended version, according to the directory authorities.
>
> --
> Cheers Felix
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Instabilities in Hydra family expected

2022-04-19 Thread Spydar007 via tor-relays
Hello,

Regarding Yourserver.se: I too recently began running an exit there.[1] I 
receive multiple abuse complaints a week, they simply forward them and close 
the ticket without needing a response.

I have been a customer of Yourserver.se for many years, back when Sweden was 
the only option for a location, back when they were only providing OpenVZ and 
not KVM, back when they would limit servers running Tor relays to 5Mbps (which 
they no longer seem to bother with).

I ran a middle relay back then, and I remember having discussions with them 
about Tor - they didn't really understand the principle of an exit relay, so I 
chose to just stick with a middle relay to be safer. Now having come back to 
relay operation I decided I would give an exit a go there - there are several 
others across their two ASNs[2][3] (majority Hydra) and having been a customer 
and having extensive contact with their team over the years I figured I am 
likely to have more of an understanding with them.

The exit did get suspended a few weeks back for "malware", and I opened a 
ticket explaining Tor and how I am not responsible for whatever they mean 
"malware" to be. They unsuspended it with the response:
> The VPS was blocked for malware.
> We don't accept this malware.
> We unspended Your VPS.

I took that to mean that the "malware" being distributed over Tor is irrelevant 
to them.

Everything has been fine since, until today (ironically) when it got suspended 
for "spam". They responded with:
> We allow TOR, but don't allow spam.
> We unsuspend Your VPS.
> We receive very much spam abuse about Your VPS.
> Please, check Your VPS.

I think they continue to misunderstand the purpose of Tor or would prefer 
people to somehow run exits without any issues whatsoever.

I do run my exit with an almost completely open exit policy (except for mail 
ports and ports they block[4]), so I plan to now set it to reduced and see if 
that helps them be ok with it. I notice the Hydra relays are already on a 
substantially reduced policy (beyond even the reduced-reduced policy), so 
perhaps this will make no difference in my case either and I will end up also 
needing to move them elsewhere. I am happy to endure with Yourserver.se though, 
I do not want my years of being a happy customer to be ended because they don't 
understand Tor well enough.

With regards alternative hosts, I recently discovered rdp.sh[5], who operate 
under a new ASN.[6] They are happy with Tor exits if you comply with their 
policy[7] (let them know first and block mail ports), and they provide 
unmetered 5 Gbps connection in the Netherlands.[8] They also run some reduced 
exits and middle relays themselves, and the operators of the bauruine family 
also began running exits a few days before me.
It's worth noting however that they don't provide IPv6 right now, and won't set 
reverse DNS PTR records on request (I tried).
They could prove to be a good replacement for Yourserver.se if you need one.

Cheers,
Spydar007

[1] 
https://metrics.torproject.org/rs.html#details/CC8732E6E34D8C1AA61A3B7FE95DDD71BCE9C880
[2] https://metrics.torproject.org/rs.html#search/as:AS43513%20flag:exit
[3] https://metrics.torproject.org/rs.html#search/as:AS52173%20flag:exit
[4] https://www.yourserver.se/knowledgebase/35/Blocked-ports.html
[5] https://rdp.sh
[6] https://metrics.torproject.org/rs.html#search/as:AS210558
[7] https://rdp.sh/docs/faq/tor
[8] https://rdp.sh/docs/faq/traffic-limit
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


[tor-relays] Bridges not being distributed

2022-03-25 Thread Spydar007 via tor-relays
Hello,

I notice (almost) all bridges are showing their distributor mechanism as None 
on Tor Metrics.[1]

There are also hardly any in the latest pool assignments file from CollecTor.[2]

Curious as to why? Is this a change that needs fixing on a bridge operators 
end, or simply BridgeDB not reporting properly?

[1] https://metrics.torproject.org/rs.html#search/type:bridge%20
[2] https://metrics.torproject.org/collector/recent/bridge-pool-assignments/
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] update obfs4proxy if you run a bridge

2022-03-22 Thread Spydar007 via tor-relays
On 21 Mar 2022, 17:46 +, meskio , wrote:
> Hello,
>
> TL;RD:
> if you are a bridge operator please update obfs4proxy to a version>=0.0.12.
Thanks, done.

Worth noting I had to adjust (on Debian) /etc/apparmor.d/abstractions/tor to 
contain:

/sys/kernel/mm/transparent_hugepage/hpage_pmd_size r,

To prevent the error:

apparmor="DENIED" operation="open" profile="system_tor" 
name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size

per [1].

And be sure to setcap the obfs4proxy binary again if running on a port<1024, as 
well as restart Tor after updating.

Cheers.

[1]: 
https://www.mail-archive.com/debian-bugs-dist%40lists.debian.org/msg1839505.html
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Bridge opening an "Extended OR listener"???

2022-03-19 Thread Spydar007 via tor-relays
On 19 Mar 2022, 07:54 +, Thoughts , wrote:
> What is this?  Should I allow the external world access to the specified
> port?
Hello,

Per the bridge setup instructions page[1], the ExtOrPort setting is a local 
communication port between Tor and obfs4. You should set it to "auto" in your 
torrc file, and it should NOT be accessible to the open world.

[1] https://community.torproject.org/relay/setup/bridge/debian-ubuntu/
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays