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

@da_667 do you have a laptop sticker that says "pcaps or it didn't happen"?

Because if not then you should get one made

@http_error_418 that is my FAVORITE saying.
@da_667 @http_error_418 amazingly I am wearing the t-shirt right now
@da_667 @http_error_418 (it's filthy cos I just ate a burrito then cleaned the kitchen)
@gsuberland
I really really do need that one! If I got a nickel every time a customer says it's not working abs then a pcap reveals their routing/firewalling/... is crap...
@da_667 @http_error_418