Post #1763160
2026-04-26 17:12 UTC
Replies (6)
-
@hankg@friendica.myportal.social 2026-04-26 17:34
@nedbat@hachyderm.io That was a very interesting exploration!
-
@mgorny@social.treehouse.systems 2026-04-26 17:44
@nedbat@hachyderm.io, "Cloudflare, can't read"? (Just deadloops on verification here.)
-
@Techychap@hachyderm.io 2026-04-26 17:56
@nedbat@hachyderm.io fascinating. From my own challenge with spam, I've come to realise that there's lots of bots on domestic machines. Luckily mine were just advertising a Russian online marketplace
-
@hk@chaos.social 2026-04-26 20:05
@nedbat@hachyderm.io This has been happening for a very long time now. A long time ago (2010 ish) we (@bytewerk@chaos.social) patched a sshd to print out username and password of each logon and always reject. Then we filtered every new attempt to make sure we have only unique combinations. In the end there was a twitter bot who twittered the user&password combinations. Unfortunately twitter has a rate limit so the backlog grew larger and larger until we stoped the experiment.
-
@switch@tenforward.social 2026-04-26 21:43
@nedbat@hachyderm.io I loved the gentle nod to genuinely curious people.
-
@wollman@mastodon.social 2026-04-26 22:30
@nedbat@hachyderm.io The one thing I'd disagree with is the advice to run ssh on a different port. It doesn't matter. The scanners will find your ssh on any port you care to stick it on. Even 443. There are more than enough of them, and few enough IPv4 addresses, to just try all 65,535 ports.