>>Oh interesting. You're right. I recently added Stem's ORPort
>>capabilities but seems I forgot to add usage examples in the docs.
>>Thanks for pointing that out, I'll add it to my todo list. In the
>>meantime I provided an example here...
>>
>>https://blog.atagar.com/april2018/
>
> Thank you!
>
On May 20, 2018 17:37:07 UTC, Damian Johnson atagar at torproject.org wrote:
>
>> There don't seem to be any examples of ORPort endpoints in the Stem
>> repository. I think Dave plans to add some more documentation as part of Tor
>> Summer of Privacy.
>
>Oh interesting. You're right. I recently
> There don't seem to be any examples of ORPort endpoints in the Stem
> repository. I think Dave plans to add some more documentation as part of Tor
> Summer of Privacy.
Oh interesting. You're right. I recently added Stem's ORPort
capabilities but seems I forgot to add usage examples in the docs.
On May 20, 2018 10:08:17 UTC, gustavo wrote:
>
>On May 18, 2018 4:25:23 PM UTC, starlight.2017q4 at binnacle.cx wrote:
>>Lately seeing escalating abuse traffic on the relay dirport, now up to
>>20k rotating source IP addresses per week.
>
>How do you detect it?
FIRST: your relays
On May 18, 2018 4:25:23 PM UTC, starlight.201...@binnacle.cx wrote:
>Lately seeing escalating abuse traffic on the relay dirport, now up to
>20k rotating source IP addresses per week.
How do you detect it?
Will tor log it in the logs where I can look for it or do you monitor the
TCP/IP stack
Hi
Am 19-May-18 um 16:28 schrieb starlight.201...@binnacle.cx:
> Dirport is a handy convenience, but is not essential to proper
> functioning of the network. Put a connection rate-limit on
> dirport and it stopped the abuser cold. Dirport traffic went
> from 15% of total back down to 1-2% where
Hi,
I didn't get your original email, it appears my spam filter is eating all your
emails.
(And a few other emails.)
At 12:25 5/18/2018 -0400, starlight.2017q4 at binnacle.cx wrote:
>Lately seeing escalating abuse traffic on the relay dirport, now up to 20k
>rotating source IP addresses per
Dirport is a handy convenience, but is not essential to proper
functioning of the network. Put a connection rate-limit on
dirport and it stopped the abuser cold. Dirport traffic went
from 15% of total back down to 1-2% where it belongs.
Nonetheless the questions posed are valid.
At 12:25
Lately seeing escalating abuse traffic on the relay dirport, now up to 20k
rotating source IP addresses per week.
The simple solution is to disable dirport, but the relay is a fallback
directory and I don't want to make a change that will negatively affect the
relay's ability to function as