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 I ran a "telnet server" for the express purpose of learning how to use systemd's socket listeners and for trolling the rest of the security team in nexpose by having the process it connected to be nyancat.
@tehfishman @da_667 if you work in an Enterprise IT Security Team (aka the Company Computer Police), they don’t do anything more than scream bloody murder that “OH MY GOD THIS HAS A VULNERABILITY!!!1!!11!!!one!” If they see TCP port 21 or 23 open on the external consultant’s report who just ran a quick Nessus TCP port scan and charged $BIGNUM dollarydoos for the privilege