download.htmldownload.htmlttsshdoc.htmlttsshdoc.htmldownload.htmldownload.htmlttsshdoc.htmlttsshdoc.htmlttsshdoc.htmlh2>

<P>TTSSH is a free SSH client for Windows. It is implemented as an extension DLL
for <A HREF="http://hp.vector.co.jp/authors/VA002416/teraterm.html">Teraterm Pro</A>.
Teraterm Pro is a superb <em>free</em> terminal emulator/telnet client for Windows,
and its source is available. TTSSH adds SSH capabilities to Teraterm Pro without
sacrificing any of Teraterm's existing functionality. TTSSH is also free and its
<A HREF="http://www.zip.com.au/~roca/download.html">source is available</A> too. Furthermore,
TTSSH has been developed entirely in Australia, and can be exported from here to
anywhere in the world (apart from places where people aren't allowed to own
cryptographic software at all :-( ).</P>

<P>To be more precise, the current version of TTSSH (1.2) includes the following
features:</P>

<ul>
<li>Compatible with SSH protocol version 1.5</li>
<li>Ciphers: 3DES, IDEA, Blowfish, DES, RC4</li>
<li>Server authentication using the ssh_known_hosts database (including the option
of adding a server's key to the database)</li>
<li>Authentication using password, RSA, rhosts and rhosts+RSA</li>
<li>Compression support</li>
<li>Connection forwarding (special handling of X11 is not provided, however)</li>
</ul>

<P>Note that TTSSH is just an SSH client and does not include any other SSH tools
(scp, ssh-keygen, ssh-agent, etc). Furthermore, because it's tied into Teraterm, it's only
suitable for interactive use. For non-interactive uses such as interprocess
communication, you want a straight port of the Unix client.</P>

<h2>What's New</h2>

<ul>
<li><strong>July 7, 1998, version 1.3</strong>: An overseas friend (thanks jch!)
was able to insert the
<A HREF="http://www.core-sdi.com/ENGLISH/CoreLabs/sshx/index.html">CORE-SDI patch</A>
to guard against the SSH insertion attack. At the same time he fixed a few bugs.
<A HREF="http://www.zip.com.au/~roca/download.html">Download now!</A>
Note that, due to an oversight, the version number in the file was not updated.
To check the version, note that TTXSSH.DLL version 1.3 is 158,208 bytes long.</li>
<li><strong>June 24, 1998</strong>: I finally wrote
<A HREF="http://www.zip.com.au/~roca/ttsshdoc.html">some documentation</A>.</li>
<li><strong>June 24, 1998</strong>: I'd just like to remind everyone that I cannot fix any
bugs at this time, because I will not jeopardize the worldwide distribution of TTSSH by
touching the code while I'm in the United States. (I'd also like to avoid prosecution and/or
deportation.)</li>
<li><strong>June 24, 1998</strong>: To work around a bug that prevents TTSSH from seeing
when a new configuration file is specified by the "/F" option, I have created a new
version of TTSSH.EXE. See the <A HREF="http://www.zip.com.au/~roca/ttsshdoc.html">
documentation page</A> for details.</li>
<li><strong>June 6, 1998, version 1.2</strong>: Connection forwarding added and a few bugs
fixed. Since I'm returning to the USA tomorrow, this will be the last release for
several months unless an overseas maintainer is found.</li>
<li><strong>June 3, 1998, version 1.1</strong>: RSA, rhosts, rhosts+RSA support added.
Default authentication options dialog box added. ttxssh.exe added.
Numerous bugs fixed (thanks DK).</li>
<li><strong>June 1, 1998, version 1.02</strong>: Another bug fix. Non-SSH sessions used to crash
at the end of the session.</li>
<li><strong>June 1, 1998, version 1.01</strong>: Oops! I released the debug version by mistake and it
didn't work for many people. Replaced it with the correct release version.</li>
<li><strong>May 20, 1998, version 1.0</strong>: Initial release.</li>
</ul>

<h2>How to Obtain and Install TTSSH</h2>

<P>Currently TTSSH is only available for Win32 platforms (Windows 95 and NT).
Support for Windows 3.1 is plausible but I don't have the tools to build it.
Perhaps someone will be able to help with this. Furthermore, it's only
available for Intel platforms. Again, I don't have the tools to compile it
anywhere else, and someone else may be able to help.</P>

<P>The following instructions will also serve to update an old version of TTSSH.
Just say "yes" whenever it asks to overwrite a file.</P>

<ol>
<li>Download and install
<A HREF="http://hp.vector.co.jp/authors/VA002416/teraterm.html">Teraterm
2.3</A> if you haven't already.</li>
<li><A HREF="http://www.zip.com.au/~roca/download.html">Download the TTSSH software package</A>.</li>
<li>Unzip it into the directory where you've already installed Teraterm 2.3.
This will create files LIBEAY32.DLL, TTXSSH.DLL and TTSSH.EXE.</li>
<li>Run "TTSSH.EXE" and the extension should be available.
You should see a new "SSH" option in the "New Connection" dialog box and new menu items
"Setup / SSH...", "Setup / SSH Authentication..." and "Help / About TTSSH...".</li>
<li>IMPORTANT NOTE: If you are in a country where the RSA patent applies (such as the USA),
then you may need to obtain
a special version of LIBEAY32.DLL that has been modified to use their implementation,
if you want to be legally squeaky clean. This version of LIBEAY32.DLL can be downloaded
from a US crypto site if you are a US or Canadian citizen in the US or Canada; see
the <A HREF="http://www.zip.com.au/~roca/download.html">downloads page</A> for details.</li>
</ol>

<h2>How to Use TTSSH</h2>

<P>There is now a <A HREF="http://www.zip.com.au/~roca/ttsshdoc.html">TTSSH documentation page</A>.</P>

<h2>What the Government Wants You to Know</h2>

<P>This code contains cryptographic software covered by US ITAR regulations
and by the laws of various countries. Its distribution and use may be
restricted by these laws and regulations. In particular, it is probably
illegal to make this code publically available at a US site.</P>

<P>When in the US (and possible in some other places) you may need to use the RSAREF-based
LIBEAY32. This is discussed further in the installation section above.</P>

<h2>What I Want You to Know</h2>

<P>All the usual free software legalese applies. There are no warranties
of any kind. The software is provided entirely "as is", and use is entirely
at the discretion and risk of the user. Enjoy!</P>

<h2>Who to Thank</h2>

<ul>
<li>This code started with Ian Goldberg's Top Gun SSH for the Pilot.</li>
<li>It makes use of Eric Young's cryptographic library, taken from SSLeay 0.8.1.
His copyright notice is <A HREF="LIBEAY.TXT">included as LIBEAY.TXT</A>. The LIBEAY32
used by TTXSSH is a plain "out-of-the-box" build.</li>
<li>This code uses the GNU zlib library (version 1.0.4). That library is
(C) 1995-1996 Jean-loup Gailly and Mark Adler.</li>
<li>The TTSSH 1.3 upgrade was done by Jonathan Hardwick, zephyr prince.</li>
<li>Finally, this would not have been possible without the cooperation of T.
Teranishi. Many thanks!</li>
</ul>

<h2>What to Do about Bugs</h2>

<P>TTSSH has been tested in Windows 95 and NT 4.0. Mileage with other platforms
may vary, but I'm interested in getting bug reports.</P>

<P>Known bugs:</P>

<ul>
<li>On some systems, you may see mysterious problems in the session such as NULL
characters (^@) appearing when you press the return key. This is caused by
Teraterm being in telnet mode, something that should never happen during an SSH
session. This is a bug in TTSSH because it should always be suppressing telnet mode.
A workaround that usually succeeds is to edit the TERATERM.INI file and change the
"Telnet=on" option in there to be "Telnet=off".</li>
<li>Patterns in ssh_known_hosts files that contain many * wildcard characters
may take excessive time to match against the hostname. The program should
fall back to a worst-case quadratic time algorithm.</li>
<li>If you connect to a host, then disconnect, then quickly try to reconnect to the
same host, there is about a 1 in 500 chance that the reconnection will fail
(in which case you should just try again). This is because we try to allocate a
privileged port between 512 and 1024 for the socket to make rhosts
authentication possible. Unfortunately, if some other socket is in a TIME_WAIT state
(i.e. closure in progress) then we may successfully 'bind' to the same port but
then 'connect' will fail, complaining that the port is already in use. This
only happens when we try to connect to the same host that the other socket was
connected too. Weird, eh? We try random ports to try to prevent this from
happening too much. If rhosts is not needed, all this stuff can be disabled; see
<A HREF="http://www.zip.com.au/~roca/ttsshdoc.html">the documentation</A>.</li>
<li>Sometimes the remote host will disconnect and the window will not close even if
you've specified "close window on disconnect". This happens when a dialog box or
message box is showing when the disconnect is detected. This is actually a Teraterm
"feature", and there's nothing I can do about it.</li>
<li>If you specify /ssh or -ssh (or /T=2) on the command line, you also need to specify /t=0
BEFOREHAND in order for things to work 100% properly.</li>
<li>Using multiple extensions at once (e.g. having SSH and SSL installed at the same time)
does not work.</li>
<li>There is a bug in the handling of the command-line options that start with
"/ssh" or "-ssh". The symptom is that Teraterm complains it cannot connect to the host,
even though it should be able to. It may also crash under some circumstances.
The work-around is make sure that the last command-line parameter is not an
"/ssh" or "-ssh" option.</li>
<li>Teraterm has a bug in the processing of the /F option for selecting a different
configuration file. Basically, TTSSH never sees this option, so it always gets its
settings from TERATERM.INI. I have made a workaround --- a new version of TTSSH.EXE that
supports a new "/ssh-f=" option. See
<A HREF="http://www.zip.com.au/~roca/ttsshdoc.html">the documentation</A>.</li>
<li>TTSSH version 1.3 reports its version number as 1.2.</li>
</ul>

<h2>What the Terms and Conditions are</h2>

<P>Redistribution and use in binary forms, without modification, are permitted
provided that the following conditions are met:</P>

<ul>
<li>Redistributions must contain the files ttssh.html and ttxssh.dll,
unmodified.</li>
<li>The conditions of the contributors must be met. In particular, if
libeay32.dll is included, then libeay.txt must be included and its conditions
followed.</li>
</ul>

</BODY>
<ADDRESS><A HREF="http://www.cs.cmu.edu/~roc">Robert O'Callahan</A></ADDRESS>
</HTML>