Comment by zamadatix
21 hours ago
Very interesting, I hadn't heard of this obfuscation before so it was well worth clicking.
Another good trick for debugging ssh's exact behavior is patching in "None" cipher support for your test environment. It's about the same work as trying to set up a proxy but lets you see the raw content of the packets like it was telnet.
For terminal games where security does not matter but performance and scale does, just offering telnet in the first place can also be worth consideration.
It made the front page when it was added.
https://news.ycombinator.com/item?id=37307708
Not everyone sees the HN frontpage every day, and sometimes especially-esoteric things spend a fairly short timespan on there.
Sadly, much fewer computer systems have telnet nowadays.
Also, port 21 is often blocked.
23 (21 is ftp)