suse unix V10 - Telnet

[Graham]

Ok, anyone know the quick answer on how to turn telnet on ... its all installed and everything but default settings dont allow it... I know they all want you to use ssh but this is on an in internal ringfenced lan

G

[SneakyNeil]

SSH is easier and better in every way.... sorry not what you wanted to hear I know! PuTTY is a small standalone client for Windows, if you google putty its #1.

[David Godfrey]

What he said, Putty is great I have been converted....

[Zumbruk]

You shouldn't really be using telnet, even on a private LAN, but;

http://tr.opensuse.org/Telnet_Server_HOWTO

This tells you how to switch telnetd on.

[ThePassenger]

Graham said:

Ok, anyone know the quick answer on how to turn telnet on ... its all installed and everything but default settings dont allow it... I know they all want you to use ssh but this is on an in internal ringfenced lan

G

SSH is a more robust protocol and as a bonus has nifty things like sftp for pushing files to the machine, even on a ring fenced internal LAN. To be honest it also feels snappier in use than telnet. Anyway sales pitch aside

But if you really do just want Telnet fire up yast and search for 'telnet', you should see it listed (it was back in the days of Suse 8). Install it and then add it to the start up sequence of the machine (again in yast). Either reboot or try something like "/etc/init.d/telenet start" and you should be cooking on gas.

[onomatopoeia]

Zumbruk said:

You shouldn't really be using telnet, even on a private LAN, but;

I hear this a lot. Why? No one has ever given a satisfactory answer as to why not on a private LAN.

I use SSH & putty, but I'd love to know why telnetd is bad on a private LAN with one user.

[ThePassenger]

onomatopoeia said:

Zumbruk said:

You shouldn't really be using telnet, even on a private LAN, but;

I hear this a lot. Why? No one has ever given a satisfactory answer as to why not on a private LAN.

I use SSH & putty, but I'd love to know why telnetd is bad on a private LAN with one user.

Telnet is old, first mainframe old and has generally been surpassed in terms of usability by SSH, as I said above whilst heading in to the farm at work I'd get faster responses from SSH (and less buggering around with cut n' paste) than I did with Telnet. This could of just been AIX's implementation of Telnet though but.

I'd also suggest that with the availability of SSHd's the Telnetd won't be as frequently updated or vetted for bugs. Some of which may be security related (which is moot) some of which may be usability related (which are valid). You also have the 'opps' factor. If I screw up and do make a machine world facing I'd much rather have SSH going 'feck off' than Telnet doing the same... just in case... whilst I repair my error.

[Graham]

ta..


heck I still use vi, for everything, and mourn edlin on pc dos

G