I guess I trigger the bot detection? All I am served with is a Rick Astley quote.<p>Turns out switching from Firefox mobile to Chrome mobile "fixes" this. Thanks for supporting the free and open internet.
We don't leave any ports open anymore. Everything is behind Wireguard. No key? Your packet goes into the blackhole.<p>Silent by default.
I like this, back when the xterm CVE was common you could probably 0wn any botter who was looking at their logs in xterm.
Not sure if it's down or if I've been flagged incorrectly as a bot<p><pre><code> Safari can't open the page "https://mirror.newsdump.org/confuse-some-ssh-bots.html" because Safari can't connect to the server "mirror.newsdump.org".</code></pre>
> The VersionAddendum will cause most poorly coded bots to hang, thus causing the botter to exclude us from their scans rather than us having to block them.<p>Why does this happen, wouldn't bots just ignore the version information?
Feel free to test your SSH bots <i>and HTTP bots</i> against mirror.newsdump.org
[delayed]
Paramiko v4.0.0 (the latest) gets past the version string, it seems, but dies instantly on failed KEX, which is another convenient incompatibility. It does mean that even legitimate SSH bots in Python will fail though.
That is likely from performing hardening in ssh-audit [1]. The way I used to block python, Go and libssh was to use a iptables string search but that capability does not exist <i>at least natively</i> in nftables.<p>[1] - <a href="https://www.ssh-audit.com/" rel="nofollow">https://www.ssh-audit.com/</a>