[tor-relays] Blocking outbound 22 or no?

[Sebastian Urbach]

Good Evening,

What Dirk just described is exactly what happened here. Timeframe matches 
and i disabled port 22 as well. Adjusting the port for your own system 
seems to be a good idea and it is working very well for me.
--
Sincerely yours / M.f.G. / Sincères salutations

Sebastian Urbach

---------------------------------------------------------------------------
Those who surrender freedom for security
will not have, nor do they deserve, either one.
---------------------------------------------------------------------------
Benjamin Franklin (1706-1790)



Am 5. Oktober 2017 20:55:54 schrieb tor-relay.dirk at o.banes.ch:

> Hello AMuse,
>
> we faced the same about 1-2 month ago. Actuall people use fail2ban which
> creates abuse mails to you provider.
> Thats not new. But recently the abuse mails have risen to numbers which
> lead us to believe there are acutally more people abusing ssh via tor
> than people really using it.
>
> In the end we disabled port 22. After all - any sysadmin who wants to
> have peace and ever looked a ssh config will have its listen port
> somewhere else than 22.
>
> best regards
>
> Dirk
>
>
> On 05.10.2017 19:08, AMuse wrote:
>> Hi all!  I'm getting a number of ISP Abuse complaints around outbound
>> ssh brute-forcing from our exit relay.
>>
>> I'm personally of the opinion that people should run fail2ban (or
>> equiv) and get on with life and I generally ignore the complaints -
>> but wondered, what are other operators doing?
>>
>> Is anyone exit-policy blocking outbound 22 to make the internet a
>> kinder place?  Is anyone refusing to on principle?
>>
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays