Re: Re: how to access machine using telnet

On 8/31/06, Felipe Alfaro Solana <felipe.alfaro@xxxxxxxxx> wrote:
Can anyone tell me how to setup my Ubuntu machine so that I can telnet
into it and control it using a remote terminal?

No ;-)

Telnet is dangerous. So, we recommend you to go with SSH:

sudo apt-get install sshd



I think it is kind of funny the way everyone predictably pops up with
a reflex reaction giving warnings about telnet and redirecting the
poster to ssh every time any topic on telnet comes up (on any mailing
list). Run away! run away! Telnet is dangerous!

A couple years ago I asked (maybe this list - I don't remember) how to
get telnet set up, and explained that I already used ssh and had a
good reason for setting up telnet. As I recall I had a dozen responses
telling me to install ssh - ignoring the fact that ssh was already
set up and in use, and that I was well aware of the 'dangers' of
telnet already.

For anyone who is unaware of why telnet is considered insecure:

"Accessing a shell account through telnet method though poses a danger
in that everything that you send or receive over that telnet session
is visible in plain text on your local network, and the local network
of the machine you are connecting to. So anyone who can "sniff" the
connection inbetween can see your username, password, email that you
read and commands that you run."
(found at http://www.suso.org/docs/shell/ssh.sdf)

In my case (some time ago) I was dealing with a headless server I was
set up on the other side of the world. (I live in Japan - server was
in Canada) I wanted telnetd to be running, but not used except as a
backup way to get in if sshd failed to work. (Which had happened once
after changing the config file.) The insecurity of telnet is that
everything is sent in the clear and passwords could be 'sniffed' on
the local network. As a backup service there would be nothing to sniff
unless I couldn't get in via ssh.

</rant>

Anyway, I DO agree that ssh is preferable over telnet. However, if you
understand and accept the risks and have some need for telnet I assume
you would do install it with something like the following:

$ sudo apt-get install telnetd

Restart inetd service:
$ sudo /etc/init.d/inetd restart

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • RE: Commentary on the seven words
    ... When I was an operating systems programmer we all too often forgot that the Operating system existed to support the application, not the other way around. ... A Because the application that we run uses a telnet client that doesn't support ssh - and that's why I can't run ssh on this system. ... I administrate one system that has 128 clients on it and it's ...
    (RedHat)
  • Re: Commentary on the seven words
    ... A Because the application that we run uses a telnet client that doesn't ... support ssh - and that's why I can't run ssh on this system. ... General Red Hat Linux discussion list ... >operating system and utility advice and assistance and there are SEVEN ...
    (RedHat)
  • Re: Commentary on the seven words
    ... routinely asked to help with enabling rsh and telnet. ... Shoot, I use SSH & all that, but if I wanted to allow it for some ... > I wrote in with a complaint that Linux will allow a process (like Tar, ... I administrate one system that has 128 clients ...
    (RedHat)
  • Re: OSR507: xm_vtcld : could not open libXm.so
    ... laptop, I can run successfully "scoadmin software" if I'm through SSH, ... LINUXLAPTOP $ telnet 172.xxx.101.66 ... Similarly cron jobs have a different environment, and cgi-bin scripts ...
    (comp.unix.sco.misc)
  • Re: SSH newbie question
    ... I had to enable SSH on one alpha in order to be able to "telnet" to my ... I didn't have to configure the mac on the VMS host and vice versa. ... Unless you take steps to block connections to it (via firewall rules, ...
    (comp.os.vms)