SSH (Secure Shell) protocol is the secure replacement of telnet.
The same privacy considerations that apply to email and files also apply to remote logins. You have every right to expect security for your interactions when you're logged in to a remote host machine:
Yes, remote logins are vulnerable in all these areas. Say you're going from here to there. If the route from here to there goes though someone else's network, then:
SSH's provides strong security for remote logins. SSH's security is transparent because it's an application layer protocol, you use SSH software to login to a remote host instead of using telnet. It supplies two-way authentication, including the server authenticating itself to you. After exchanging keys, your entire session is encrypted, including your password and everything that you send to the host server and everything it sends to you. The best thing about SSH is that all this security stuff goes on behind the scenes.
It's no harder to switch to an SSH secure remote login application than it is to change from one vendor's telnet to another's.
This is all why the ACCC is requires SSH for remote logins to its machines and SFTP for secure file transfer.
Connecting to servers such as argo and webhost at UIC require the use of either SSH or SFTP.
ACCC has made SecureCRT and SecureFX available at no cost. For instructions on how to use these clients, visit How do I use SSH and SFTP on Windows?
For instructions on how to use the SSH built-in to Mac OS X and no-cost SFTP software for Mac OS X, visit How do I use SSH and SFTP on Mac OS X/macOS?
OpenSSH is almost always bundled with Linux, which contains SSH and SFTP clients.
PuTTY is a free, commonly-used SSH client for Windows and Unix that can be used as well.