On Thu, Feb 04, 2021 at 01:20:58AM +0200, s7r wrote:
> Indeed the defense is triggered more often than I expected. Very nice.
Btw, a better version of the #2667 patch is now included in all of the
current Tor releases: 0.3.5.13, 0.4.3.8, 0.4.4.7, 0.4.5.5-rc.
So if you are still trying out my
Roger Dingledine wrote:
Hello friendly relay operators,
Another day, another weird thing with the Tor network. This time we
have some jerk bombing the directory authorities with directory fetches,
and doing it via exits:
Roger Dingledine:
> On Fri, Jan 29, 2021 at 12:34:28AM +0100, nusenu wrote:
>> If dir auths (some or all) are willing to share (privately or publicly) the
>> distribution of
>> attack load (frequency, bandwidth, ...) by exit source IP in total or
>> relative values
>> I can correlate this data
On Fri, Jan 29, 2021 at 12:34:28AM +0100, nusenu wrote:
> If dir auths (some or all) are willing to share (privately or publicly) the
> distribution of
> attack load (frequency, bandwidth, ...) by exit source IP in total or
> relative values
> I can correlate this data to strengthen a hypothesis
Unless you already ruled out that hypothesis by looking at the attack
distribution by source IP:
If dir auths (some or all) are willing to share (privately or publicly) the
distribution of
attack load (frequency, bandwidth, ...) by exit source IP in total or relative
values
I can correlate this
Have a tor exit running in the US ; fingerprint is
3DE567C1350C0E858C6147AECB06EA9B3EAF3261 and OR address is
71.174.105.126:9001
Just built and launched the ticket-2667 branch; came up as:
[notice] Tor 0.4.6.0-alpha-dev running on Linux with Libevent
2.0.21-stable, OpenSSL 1.0.1t, Zlib
Hello friendly relay operators,
Another day, another weird thing with the Tor network. This time we
have some jerk bombing the directory authorities with directory fetches,
and doing it via exits:
https://lists.torproject.org/pipermail/network-health/2021-January/000661.html
The network is
