The scope of this CVE and the response to it are genuinely wild.
It's crazy to think that some dude is singlehandedly responsible for ultimately ending the telnet era in such a definitive way.
One for the history books.
When I was an intern for some reason they issued me a voip phone for my desk. One day I got bored and figured out I could telnet into it. Nothing interesting but it was still a fun moment for me!
So eleven years ago someone put a backdoor in the Telnet daemon.
Who?
Where's the commit?
It's nice to not see C being blamed for once! ... Just good old lack of reasoning (which is most C's codebase downfall, agreeably).
> Someone upstream of a significant chunk of the internet’s transit infrastructure apparently decided telnet traffic isn’t worth carrying anymore. That’s probably the right call.
Does this impact traffic for MUDs at all? I know several MUDs operate on nonstandard Telnet ports, but many still allow connection on port 23. Does this block end-to-end Telnet traffic, or does it only block attempts to access Telnet services on the backbone relays themselves?
The design of telnet and ssh where you have a daemon running as root is bad security that as shown here is a liability, a ticking time bomb ready to give attackers root.
Stranger article. I wasn't able to get the main point of this article. Strangely written, but hey - I'm nob native by any means.
ps.
telnet SDF.org
just works...
I used to telnet into my POP3 account and check email by protocol. Shucks.
I still used telnet today (had to). Unsure of the patching here. But its definitely locked down to a subset of internal use only.
telnet isn't just for ... telnet.
$ telnet smtp.example.co.uk 25
HELO me
MAIL FROM: [email protected]
RCPT TO: [email protected]
DATA
.. or you can use SWAKS! For some odd reason telnet is becoming rare as an installed binary.Your cookie banner is very inconvenient and made me leave your website and not read the article
telnet + shijack = good times
The pattern points toward one or more North American Tier 1 transit providers implementing port 23 filtering
[dead]
Why would somebody read something that somebody couldn't be bothered to write? This article is AI slop.
Why are people still using telnet across the internet in this century? Was this _all_ attack traffic?
(OK, I know one ancient talker that uses it - but on a very non-standard port so a port 23 block wouldn't be relevant)