Setting Up the SSH Client for Windows

1) Downloading

The SSH Secure Shell Client for Windows can be downloaded from:
http://osusls.osu.edu/upgrades/sshwnx.html
with a valid OSU username. Or you can pick up the software CD from Computer Support.

2) Installing

Double click on the installer. Click on Next on the first screen, then on the License manager screen, click Yes to accept. On the Select Components screen, click Next to take the default. The installer will then copy the needed files. Click Finish to complete the installation.

Now we will configure the client. Double click the SSH icon on the desktop, or go to Start -> Programs -> SSH Secure Shell -> Secure Shell Client. Go to Edit -> Settings. On this screen you can enter the host you want to connect to, as well as your username. (Note, you can change this at connect time.) In the left hand pane click on Tunneling. Make sure that Tunnel X11 Connections has a check mark in it.

Now go under File -> Save to save these as your default settings.

3) Getting Connected

Go to File -> Connect, or simply press Enter to connect. After you enter you password, you will be prompted to accept a host key, click Yes. (Note, this will happen the first time you connect to any host, but should not happen on subsequent connects.) At this point you should be connected, and now can do whatever you would do in telnet.

4) Secure File Transfer

Start SSH and log into a machine. Then choose Window -> New File Transfer. You'll now see all the files on your Unix account. Navigate through your folders until you find the file you want. Then just drag it to the desktop.

To upload, navigate to where you want to place the file on the unix machine, then drag the file from the PC into the file transfer window.

5) Using X Windows through SSH

Passing an insecure protocol through SSH to make it secure is called tunneling. We're talking about tunnelling X here.

(Note, if you start X windows through SSH, you must leave the original SSH window open, as it is tunneling the connection. If you aren't tunneling X you can logout of the SSH window once your windows come up.)

5a) Using Xwin32 X Windows through SSH

Go to Start -> Programs -> X-Win32 -> X-Config. On the Security tab Currently it is blank, meaning anyone can access your machine. Click on Add. Add the following hostnames:
localhost

On the Sessions tab do the following: leave everything blank.

Start Xin32 as normal, and then log in via SSH. Now you can start any X clients you want or sh .xsession & to get your regular windows. You DO NOT setenv DISPLAY or run setdisp. SSH already does this for you. If you do that you are not tunneling.

5b) Using Exceed X Windows through SSH

Go to Start -> Programs -> Exceed -> Xconfig. Open Security. The radio button file should be checked, go ahead and click Edit next to the filename. Under the # comment lines there may be zero or more hosts. Add the line:
localhost
on a separate line right after the last comment. If you plan on connecting without tunneling you'll want to leave these hosts in, but remember anyone on those hosts can see your screen, and what you type. Click OK in the Security window, and then close Xconfig.

Start Exceed as normal, and then log in via SSH. Now you can start any X clients you want or sh .xsession & to get your regular windows. You DO NOT setenv DISPLAY or run setdisp. SSH already does this for you. If you do that you are not tunneling.

Appendix 1: Tunneling Protocols Other Than X

For most users this should not be necessary, however if you wish to continue running Eudora which does not support secure mail, you will need to do this. This is the example used here. (Note, we do not encourage doing this as Eudora is unsupported by the manufacturer.)

Open SSH on your PC. Under Edit -> Settings, you will want to click in the left hand pane Outgoing, which is under Tunneling. In this window you will want to add a new tunnel. Fill in the following: Name should be pop3, listen port 110, Allow Local Connections Only should be checked, Destination Host should be mail.stat.ohio-state.edu, and Destination Port should be 110. Click OK, and then under File -> Save save the settings.

In Eudora you should now set under Tools -> Options click on Getting Started in the left pane. Set Mail Server (Incoming) to localhost.

Now, to check your Eudora mail, you need to log into the unix machines using SSH. Next you can start Eudora and it should work normally.

Since you have to log in anyway, we recommend using pine at this point, and then using the File Transfer feature for any attachments.

Appendix 2: Additional Information

There are two standards SSH1 and SSH2. SSH1 is more common at this time and does not have the secure file transfer, sftp, built it. Also, the current SSH2 client (2.3) does have SSH1 compatibility, but if you downloaded before September 1, 2000, you may have the 2.2 client which only does SSH2.

We have another SSH client that will fit on a floppy if you want to take it with you when you travel. This smaller client is an SSH1 client and does not have the file transfer capabilities.