Am 05.10.2017 19:08 schrieb AMuse:
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/05/2017 08:55 PM, tor-relay.d...@o.banes.ch wrote:
> 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.
+1
disabled exit pot 22
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
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
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
