SSH Guide: Index
Back to main Help index
Hostname: openoffice.org
Local port: 2401
Remote port: 2401
Username: tunnel
Your passphrase: [what you chose]
Hardly surprising, isn't it, that tunneling
using Mac OS 9 is trivially easy? The concepts are the same as for Windows,
Linux, or Mac OS X, as are the numbers, etc. But, in a nutshell, here's what
you do. It's a two-step process. First, you must configure MacSSH, then configure
the CVS client.
Configuring MacSSH
- Download the latest version of MacSSH,
which is characteristically easy to use, is free, Open Source, and offers
superior performance.
- Configure it by clicking on the "Favorites" pull-down menu in
the top-navbar.
- Click on the "New" button.
- Enter a name for this favorite. If it is going to be your default, don't
bother.
- Host Name: openoffice.org
- Port: 22
- Terminal: default
- Go now to "SSH2" tab.
- Encryption: 3DES
- Authentication: MD5
- Compression: zlib
- Method: Local TCP port forward
- Local port: 2401
- Remote host: localhost
- Remote port: 2401
- You now must initialize (create) your SSH2 key pair. Click on the "Initialize
SSH" button. Follow instructions.
- Export your key (that is, put it elsewhere) by clicking on the "Export"
button. This allows you to easily place it in a directory or folder for submission
as an attachment to support@openoffice.org.
- Once your key has been loaded by the helpful and friendly staff at OpenOffice.org,
you will be notified; and then you will be able to establish a tunnel.
- And, as is the case with tunnels: once established, there is no shell. At
most you will receive a message in a window saying that you are connected.
That is all. Leave this open, though you may minimize the window.
Two free clients for Windows provide SSH tunneling:
- TTSSH, an open-source add-on to Tera Term Pro
- PuTTY, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator.
As with the Mac clients, the important things to keep in mind are
the hostname and the port numbers. For both terminals, the
configuration process is straightforward. Because TTSH is an add-on to
Tera Term, it means you have to go through that one extra step before
SSH functionality is possible. [A fuller description of tunneling with
TTSH is being drafted and will be posted when finished. For now,
please see TTSH's
website.]
PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.
Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below.
The following illustrates the procedure; we will use SecureCRT (version 3.1.2):
- Open a new session, specifying "SSH1" in the pull-down menu.
- For "Hostname," enter "thisdomain.com."
- Click on the "Advanced" button by "Hostname."
- Once in the Advanced section, click on the "Port Forwarding" tab.
- For "Local port," enter "2401."
- For "Remote port" enter "2401."
- For Username, enter "tunnel."
- For User password, enter "tunnel."
- For "Remote hostname," enter "localhost."
- Enter "Save" and "OK" to exit the dialog box.
- Back in the main connection page. . . .
- Leave the defaults for "Cipher" and "Authentication" as they are.
- Click on "Connect."
- The server should then prompt for your password. It is "tunnel."
- If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. Answer yes.
- You are now tunneling.
- The terminal screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS securely.
We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, Tunneling using Cygwin. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.
Back to main Help index