How to enable SSH (Secure Shell) on Router
SSH (stands for “Secure Shell) is the protocol the campus IT department wants you to use for command-line (or shell) access to a campus Unix server. (For those of you who know the term “telnet”, SSH is a newer, more secure, replacement for it — when you login to a server, telnet transmits your password in the clear over any intervening network; SSH encrypts it.) The SSH protocol is provided by a variety of freeware or commercial software products. IT has installed a freeware version of an SSH client on most (all?) public Windows machines in campus labs and its license permits students and faculty to download and install it for personal use at home.
To use SSH, find the “SshClient.exe” executable somewhere (IT moves its shortcut around from time to time here on campus to keep us guessing, so I’ve given up trying to keep this web page up to date) and double-click it to bring up a window that looks like so:
If the dialog box, below, doesn’t come up automatically, hit the Quick Connect button to the upper left there and you’ll get a dialog box like so:
From on campus, you can actually just type in “sun” or “prclab” by itself (they’re actually aliased to the same physical machine); only if you do this from off campus will you need sun’s fully qualified domain name, or sun.pr.erau.edu, as shown in the figure, above. On campus, all our machines are on a first name basis with each other 😉
Port Number and Authentication Method you should just leave alone — the default values (shown) are correct.
If the machine you’re trying to connect from has never conected to your intended destination before, you’ll get another technojargon filled dialog box asking you about public keys and authentication and stuff like that; just keep clicking “yes” until you get connected and see the screen as shown above. (Lab machines get reset every night so they always require you do do this.) Once you’ve connected to the Unix host, you have to type your Unix commands in via the keyboard. When using this SSH Secure Shell Client, you can’t click or drag or do much else of interest inside the window with your mouse. The contents of the window are being provided by the shell on the Unix host and it won’t know where your Microsoft Windows mouse/cursor is.
- The Windows mouse will still work outside the SSH Secure Shell Client window and it can even select buttons, menus, and menu items from the Windows menu bar and toolbars at the top of the window, but it won’t do much interesting inside the window: SSH Secure Shell Client provides only a simple-minded protocol; it only passes your keystrokes to Unix — the mouse/cursor coordinates are not part of the deal. For that, you’d need a more elaborate protocol like Xwindows.
Anyway, you’re now logged into the Unix host you selected and as can be seen in the figure above, Unix is showing you a command line prompt (followed by a blinking cursor), indicating that Unix is ready for you to type in commands to tell it what to do. (The ‘%‘ sign, the command line prompt, is also known as a shell prompt, Unix prompt, command prompt, and sometimes, just as a prompt.)
- As you type in characters, Unix reads them from the keyboard and echoes them back on the command line display, moving the blinking cursor over to the right as it does so. When you hit the “Enter” key on your keyboard, Unix treats the line of text you entered as a command and, if all goes well, probably does something that approximately resembles what you thought you meant to ask for, maybe. After executing your command and perhaps displaying all sorts of weird other stuff that the command tells it to, Unix then eventually displays a new prompt on a new line and waits patiently for you to type and enter a new command. That’s why this is called the command line mode.
- Check the operation of your “Backspace” or “Erase” key. If it doesn’t erase the last character typed but instead displays something funny like ^H, you’ll need to remap the key binding. (You shouldn’t have any problem with the backspace key on campus machines, but if you install SSH on a personal machine, it’s possible [although unlikely] that you may run into this problem.)
Link here: MediaFire