Thanks for your input, Tim.
You are correct that I have not taken into account the IPs which are not in
the consensus.
My exit nodes are regularly attacked -- what caught my attention was not
the fact that an extra gigabit of traffic was flowing in, but rather the
way it was (*and still is*, on o
> On 22 Jul 2017, at 08:00, Matt Traudt wrote:
>
> Now, to my observations and the post that was referred to:
>
> /I clearly failed to clarify/ that the "suspicious" traffic which caught
> my interest was about non-Tor IPs entering the network through my exits.
How do you work out what a non-T
>> Message-ID: <> kp_uymv--...@tutanota.com> >
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello
>>
>> A few users have detected suspicious activity around certain Relays in the
>> network. There could be Time Confirmation Attacks happeni
There could be Time Confirmation Attacks happening currently on the
> Live Tor Network.
>
> If any Tor dev see this, Please Start Checking The US Relays in the network.
> --
> Securely sent with Tutanota. Claim your encrypted mailbox
On 7/21/17 12:56, Matt Traudt wrote:
> [This sender failed our fraud detection checks and may not be who they appear
> to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]
>
> On 7/21/17 12:12, 0dayshoppingsp...@tutanota.com wrote:
>> Hello
>>
>> A few users have detected suspicious
I was under the impression that HidServDirectoryV2 was an obsolete
config option. I run 0.2.9.11
On 7/21/2017 3:42 AM, Scott Bennett wrote:
Vort wrote:
Your message prompted me to check logs, and on one relay I see the following:
Similar thing for me:
Jul 19 00:08:27.000 [notice] Circuit
On 7/21/17 12:12, 0dayshoppingsp...@tutanota.com wrote:
> Hello
>
> A few users have detected suspicious activity around certain Relays in
> the network. There could be Time Confirmation Attacks happening
> currently on the Live Tor Network.
>
> If any Tor dev see this, Please Start Checking Th
Hello
A few users have detected suspicious activity around certain Relays in the
network. There could be Time Confirmation Attacks happening currently on the
Live Tor Network.
If any Tor dev see this, Please Start Checking The US Relays in the network.
--
Securely sent with Tutanota. Claim you
Vort wrote:
> > Your message prompted me to check logs, and on one relay I see the
> > following:
>
> Similar thing for me:
>
> Jul 19 00:08:27.000 [notice] Circuit handshake stats since last time:
> 3571/3571 TAP, 41180/41180 NTor.
> Jul 19 06:08:27.000 [notice] Circuit handshake stats since l
> Your message prompted me to check logs, and on one relay I see the following:
Similar thing for me:
Jul 19 00:08:27.000 [notice] Circuit handshake stats since last time: 3571/3571
TAP, 41180/41180 NTor.
Jul 19 06:08:27.000 [notice] Circuit handshake stats since last time: 2054/2054
TAP, 29181
On Fri, 21 Jul 2017 10:24:39 +0100
Pascal Terjan wrote:
> Last night for 4h30 (until VPS provider shut it down) one of my middle
> relays seems to have got in a bad state where it was using 100% CPU
> continuously
>
> It was not using much bandwidth, about 4MB/s, but reading the logs it
> seems
Last night for 4h30 (until VPS provider shut it down) one of my middle
relays seems to have got in a bad state where it was using 100% CPU
continuously
It was not using much bandwidth, about 4MB/s, but reading the logs it
seems it was getting a lot of circuit requests (70K/minute initially,
100K a
12 matches
Mail list logo
