Don't use telnet when you can have ssh.
Telnet offers NO encryption, and all input and output, including the login process itself, depends completely on the implementation (i.e. OS and its configuration). Typical causes for errors are user-defined prompts, fortune cookies, and non-default shells. While it is possible to setup telnetd in a way that only access via the loopback adapter is allowed, it is hard to do so and it is easy to remove the restriction by accident.
Ssh, on the other hand, is encrypted by default, the login process is independant from the I/O from/to the virtual terminal, and you can invoke a remote process without fiddling with the shell. It is possible (and recommended practice) to use certificates instead of passwords, so there is also no need to store a password in a script or configuration file.
Of course, CPAN has SSH modules. At least one invokes the installed ssh binary, at least one implements the SSH protocol in Perl (and/or XS).
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply] |
Don't use telnet when you can have ssh.
Correct - if I have encryption, and if encryption is important, ssh is the better way to go. There are many approaches, and it really depends on the concrete environment which one is best to use.
--
Ronald Fischer <ynnor@mm.st>
| [reply]
[d/l] |