Protect Your Sessions:
Secure Shell
By
Severed Dreams
If you use telnet, read this. Telnet is broken. Yes, I'm sure it works just fine for you. Yes, I'm sure that it allows you to log into your remote host and do all sorts of things, like editing web pages, creating new files and deleting old files. The problem is that anyone between your computer and the computer that you're connecting to can monitor your session, and then log in as you and have just as much power as you have over your web sites. If this doesn't make your blood run cold, then consider the following example.
You sit down at your computer. You pull up a DOS prompt (or a shell window if you run Linux/Unix/os X, or your favorite telnet program for Windows or mac). You type in "telnet yourhost.com" and wait a moment while you wait for the other computer to respond to your attempt to open a connection by asking who you are. Now while you are waiting, all the technical things that the computers do while setting up the connection gets put into small fragments called packets. Now you can think of a packet as a tiny envelope that takes a small amount of information from your machine and sends it to the other machine. However, to get there, your machine hands it to another machine, which hands it another machine, and so on, until it gets to the destination machine. Then the same process gets reversed backwards.
So far so good. In fact, you're probably starting to get bored and impatient. So here's the deal. Packets are not envelopes. They're more like post cards. Your computer isn't handing a sealed envelope to someone trusted at the other computer and so on to the destination. Instead, you hand a post card to maybe your neighbor, who then maybe hands it to their wife, who then passes it around work, then maybe it finds it's way into the hands of a bum on the street corner, and then eventually probably makes it's way to it's destination. Now, to follow through with the metaphor, imagine your user id and password written on the back of that envelope. Anyone who happens to take a look in transit can impersonate you and the computer on the other end won't know the difference. Scared yet?
Fortunately, since mainstream information technology has known about this problem for years, most of the hard part about protecting yourself has already been taken care of. Generally the way to protect yourself is to encrypt your telnet sessions. The most common way of doing this is by using a program called secure shell or ssh. If your hosting provider doesn't support ssh, you might want to consider looking for a new provider.
If you're running Linux, you're in luck. You've probably already got it installed (the same may be true for Mac OS X, I don't know, give the following command a try). Simply type "ssh"
Generally the syntax for command line ssh is: ssh -l
In other words: ssh <- the program command name -l <- a switch saying that you're about to write your login name [user id] <- your login name for the remote server [remote host] <- the host name of your remote server, for example server.com Then it will prompt you for your password. [password] <- your password for the server.
If you're running another operating system, just do a google search (http://www.google.com) for ssh client (your operating system). You'll find some for the command line that uses the same syntax as above. You'll find graphical programs. You'll find free programs. You'll find programs that cost money. Take a look and play around with it. If you need further advice, send me some e-mail.
Severed Dreams
Albert Schweitzer




