Secure Protocols: SSH, SCP & SFTP
Connecting to the Internet involves risk. Some of those risks were never anticipated when software was created, so many applications that universities have used for years are no longer considered safe. The primary reason for this is that all transactions take place in "clear text". This means that when you log in to a server during a telnet session, for example, your username and password are transmitted to the server as plain text that anyone can read. All it takes is the right tool to view the data as it passes by.
This has generated great concern in recent years. Users who have access to sensitive data and systems are exposed to possible compromise, with the resultant potential loss of data or compromise of critical servers. To alleviate this problem, a number of secure applications have been developed. One of these is called "SSH" (or secure shell.) This application takes the place of telnet, which is insecure, and uses encryption to protect both the exchange of username and password as well as all data that is passed between the remote client and the network server.
SSH works in a similar manner to telnet, and many of the interfaces that have been developed look just like the telnet clients that users have become accustomed to. For this reason, there isn't a long time needed to adjust to using the new technology. You just simply install the software and begin using it.
Two other secure applications are "SCP" (secure copy) and "SFTP" (secure ftp) which take the place of FTP (file transfer protocol.) SSH, SFTP and SCP are enabled on all our IR Unix servers. IR servers no longer accept insecure telnet and ftp logins (except for anonymous ftp downloading.)
There are a number of SSH, SFTP and SCP clients available for use. They are listed here in no particular order for your convenience and do not represent an endorsement by UT Dallas Information Resources Department. Some of them are freeware. Others are commercial products. As with any software, you should try the software out and make sure it's compatible with your computer before using it in your daily work.
Please note: UT Dallas only supports SSH version 2.
The clients listed below have been confirmed to work with SSH version 2
|Windows Clients||MAC clients||Other Clients|
|SSH Tectia Client
Putty (ssh, sftp and scp)
WinSCP (scp & sftp only)
ZOC for Windows
Fugu (ssh, sftp & scp)
Cyberduck (sftp only)
JellyfiSSH (ssh only)
dataComet-Secure (ssh only)
|ZOC for OS/2
pssh (ssh for the Palm OS)
TuSSH (ssh for the Palm OS)