Re: [tor-relays] CPU saturation attack/abuse

Dear Dhalgren Tor, I have been running a middle node with the ingress connexions being 5-10% fewer than egress connexions since it started about 11 months ago. changing Tor versions twice has not made any difference in this, the current version being 0.3.2.10 that came out yesterday. But I'm

Re: [tor-relays] CPU saturation attack/abuse

Found other ones: December 24 where egress was much higher then ingress (but crypto-workers were pegged, not main thread). December 28 & 29, attack like today. Feburary 1 & 2, like today with ingress higher than egress. In today's and the latter-two above the main event thread was pegged

Re: [tor-relays] CPU saturation attack/abuse

On Sun, Mar 4, 2018 at 7:06 PM, Toralf Förster wrote: > On 03/04/2018 07:41 PM, Dhalgren Tor wrote: >> the main event-worker thread >> going from a normal load level of about 30%/core to 100%/core and >> staying there for about 30 seconds; > I do wonder if this is just

Re: [tor-relays] CPU saturation attack/abuse

On 03/04/2018 07:41 PM, Dhalgren Tor wrote: > the main event-worker thread > going from a normal load level of about 30%/core to 100%/core and > staying there for about 30 seconds; I do wonder if this is just the normal behaviour when - IIRC correctly - consensus documents are compressed before

[tor-relays] CPU saturation attack/abuse

Upgraded exit to 0.3.3.3 and now seeing a curious CPU saturation attack. Whatever the cause, result is the main event-worker thread going from a normal load level of about 30%/core to 100%/core and staying there for about 30 seconds; then CPU consumption declines back to 30%. Gradual change on