Change Telnet cmd line to SSH

[Nicocaps]

Why not made that change? I think that should be more secure.

Telnet VS SSH

Telnet, by default, does not encrypt any data sent over the connection (including passwords), and so it is often practical to eavesdrop on the communications and use the password later for malicious purposes; anybody who has access to a router, switch, hub or gateway located on the network between the two hosts where Telnet is being used can intercept the packets passing by and obtain login, password and whatever else is typed with a packet analyzer.


SSH uses public-key cryptography to authenticate the remote computer and allow it to authenticate the user, if necessary. Anyone can produce a matching pair of different keys (public and private). The public key is placed on all computers that must allow access to the owner of the matching private key (the owner keeps the private key secret). While authentication is based on the private key, the key itself is never transferred through the network during authentication.
SSH only verifies if the same person offering the public key also owns the matching private key. Hence, in all versions of SSH it is important to verify unknown public keys, i.e. associate the public keys with identities, before accepting them as valid. Accepting an attacker's public key without validation will authorize an unauthorized attacker as a valid user.

[R. Ludwig]

if you want this extra security, why not use an ssh tunnel?

[Nicocaps]

I've answered my question with another ...

And .. Why not securing the program natively?
Telnet, should be prohibited in the development of the applications. I see no complication at the level of programming to give the utility of local connections are via Telnet, and remote connections using SSH to provide security.