[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Re: re. The attacker is back and bypassed the new anti-DoS mitigation



Yes guard and hsdir flags

Sent with Proton Mail secure email.

On Wednesday, November 11th, 2026 at 9:36 AM, cloudwaddie via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote:
Are only guard nodes seeing this?

I run a middle node, exit node, but am waiting for them to become old enough to start becoming used in circuits...

I am about to start my new node (that I hope to evolve into a guard), and don't want it to become under constant load.

(new to the mailing list, so don't have much context)

Thanks!

On Wednesday, 11 November 2026 at 04:46, kullikovana via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote:
I get attacked every week when i get the flags back. My relay is 53 days old and ive had six or seven attacks cant even remember anymore and to be honest this should not be like a second job giving free bandwidth.

Sent with Proton Mail secure email.

On Tuesday, November 10th, 2026 at 7:09 PM, code9n via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote:

These attacks weren't mitigated at all on my one relay (guard):
6AD7A3E682FE74BDFE34AC0F0D17714480BA773B  ,
 by the recent updates to Tor (0.4.9.15 and 0.4.9.16) that I can see.

In fact the effects of this attack have been so devastating it may be useful as an example of how bad it can be - see metrics for the last few / 6 months.

My own laziness / time constraints are undoubtedly the cause, not blaming Tor.

If anyone can give a quick summary of recent advice that could help that would be good.  Like make <these> changes to torrc and / or run <this> script.  I know such advice has been in the mailing list - (refer to above laziness / time constraints comment).

  regards,



_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx