I tried all fucking day to use docker/docker-compose to set up a telnet server. port 23 was exposed, port 23 was forwarded on the host, ss -antl4 showed me that port 23 was listening, I try to telnet in to the host IP address connection refused, FU. check docker's iptables, nothing denying me access to the docker image. I try and I try and I fucking try.

I create an LXC container on proxmox, manually install telnetd, systemctl start telnetd "okey dokey :)" telnet to the LXC container that has a direct IP on my home network, no fucking problems.

A 32-Year-Old Bug Walks Into A Telnet Server (GNU inetutils Telnetd CVE-2026-32746)

A long, long time ago, in a land free of binary exploit mitigations, when Unix still roamed the Earth, there lived a pre-authentication Telnetd vulnerability. In fact, this vulnerability was born so long ago (way back in 1994) that it may even be older than you. To put the timespan

watchTowr Labs
turns out debian bullseye's version of telnet doesn't support SLC (Set Line Character) options, at least accord to the proof of concept (or... it could be patched already? maybe?)
the telnet honeypot running on twisted did a better job than an actual telnetd. 🤔
GitHub - 0xNslabs/telnet-honeypot: A simple, low-interaction TELNET honeypot server in Python for easy network traffic monitoring

A simple, low-interaction TELNET honeypot server in Python for easy network traffic monitoring - 0xNslabs/telnet-honeypot

GitHub

I will say that either there's something weird about the bug, or the telnet server because it kept saying "DO LINEMODE. I WANT LINEMODE SLC." and the server would respond "YES. I CAN FUCKING DO THAT."

client: DO LINEMODE. I WANT LINEMODE SLC

server: "WE JUST FUCKING HAD THIS CONVERSATION". Until I killed the PoC script.

@da_667 I think you’re declaring that you have the capability endlessly (“do”) and never stating you actually want it enabled (“will”)