how to setup /run telnet server

[Craig Hagerman]

On 3/26/06, Alan McKinnon <alan at linuxholdings.co.za> wrote:
> So now I often leave telnet
> configured but not running and only allowing connections from one
> specific machine. Before making changes to ssh, start telnet and kill
> it as soon as ssh is verified as correct. If I do something stupid in
> those few minutes, at least I can use telnet to get back in
>

Yeah. That's what I was thinking of doing. I know that there are
insecurities with telnet (passwords sent in the clear for example),
but I think that the threat level is overblown. The same as everyone
preaches about having passwords that are impenetrable to dictionary
attacks ... but it is pretty rare to have someone do an all out
password cracking attack on you. It is FAR more likely that nefarious
people will use social engineering to gain access, or use a phishing
web site, etc. Having a telnet server set up listening on a
non-standard port, only paying attention to one other machine and
almost never having any connections anyway is not high on my list of
threats.