Date: Fri, 14 Dec 2018 04:56:02 +0000 From: co...@sdf.org Message-ID: <20181214045601.ga12...@sdf.org>
| The maintenance burden is as follows: | | - Y'all seem to think it's totally reasonable to telnet in the open | internet | | This means it begs for a rewrite | | - You'd want some esoteric functionality preserved | | This means rewriting it isn't going to happen How does any of that change if telnet were in pkgsrc ? Except that then it would probably need a bunch more work as pkgsrc runs on more than NetBSD. Futther, telnet is just fine on the internet - it is, after all, the internet's first application protocol, so it has kind of proved its worth. Sending passwords cleartext isn't a good idea, but that isn't always what it is used for - many of the other older protocols (FTP, and its offshoot SMTP come to mind) are based upon telnet and the telnet client is useful for testing them, and as others have said, it has many local LAN type uses (precisely because it is supported everywhere.) It does no harm as it is, if you don't use the client, all it does is occupy a couple of hundred blocks (nothing), the server is not enabled by default, and it is even smaller. kre