UT Dallas has adopted a policy of no longer allowing insecure protocols to be used for remote access. The purpose of this policy is to ensure that everything you do that involves passwords is protected from attack. Things such as telnet and ftp (file transfer protocol), that used to be the norm, are no longer allowed because everything you do with them is done in "clear text". If an attacker can see the traffic (by intercepting the traffic between your computer and the UT Dallas network), the attacker can capture your login id and password as well as every keystroke you type. This inevitably leads to further compromise, putting all your data at risk, including account numbers and other information that can be used to steal your identity or defraud the university.
In some cases, a simple reconfiguration of the application you are presently using is all that is required to convert from insecure use to secure use. This is especially true in the case of email clients that you use but may also be true for the clients you use for telnet and ftp.
The following links provide information to assist you in configuring the applications you normally use or to applications that can take the place of the ones you use now.
SSH (replaces telnet) & SCP/SFTP (replaces ftp)
- Using SSH Instead of Telnet
POPS (replaces pop)
- If you're using POP for email, you should convert to IMAPS. POP removes your mail from the server, rendering it unavailable from any other computer you use and using up space on your hard drive. IMAP, on the other hand, leaves the mail on the server, meaning you can access your email from any computer in the world and see all the emails you've saved in folders. If you want to continue using POP, you must convert to POPS. Your client's help files should explain how to do that.
Connecting securely to Exchange
- Encrypting Exchange (on campus connection)
- RPC Over HTTP (remote connection)