|
|
|
|
|
by sagonar
3518 days ago
|
|
I think that from an end users point of view SSH is as simple as telnet.
Sure there are ways to use ssh keys and so on, but the base operation is as simple, ssh machine instead of telnet machine. Regarding need to download ssh, the same has been true about telnet since (at least) windows 7.
(Telnet is NOT included by default in windows 7) Warnings about server key change, is something i feel happens very rarely with a workaround described in the error message. I feel this is a very minor issue The other ssh added complexity is optional stuff. and is something i feel made ssh better than telnet, example:
You can forward X11 connection between unix machine using ssh.(Sure you use telnet and xhost/ DISPLAY et.c ) SSH-keys are also a optional feature, that are not forced on the user, but can simplify remote login. Sure there are more complexity inside ssh and the protocol, but the simplest use of ssh is about as simple as telnet. |
|
The protocol itself is a total mess. Having implemented servers for the Telnet protocol, I can say that Telnet is a little bit of a mess, but SSH is a total nightmare by comparison.
You're right though, that if you look at a very tiny slice of SSH then it almost looks like SSH is simpler than Telnet, once you've gone through the work of generating a key pair, securing the private key, and installing the public key on your server.