SSH for Windows|
Download and install SSH for Windows|
TSSH has been upgraded to 1.5.4
There is no SSH version 2 client freely available for Windows.
The two public domain clients I could locate are SSH version 1, so a compatibility with SSH version 1 is needed on the server.
It comes in 2 files:
Note: You should not use the default icon created on the Windows desktop, this icon is a shortcut to the NON-secured version of Tera Term Pro. Make sure to use the secured version as mentionned in point 4. above.Note: TTSSH is written to use a privileged port (under 1024)
If the local network filters out privileged ports (in order to disallow rcommands for example) TTSSH has to be setup to use non-porivileged port (above 1024). This is done adding the following line to C:\autoexec.bat:
Authentification with rhosts will not be enabled anymore.
Get the file ci98274.zip
1024 37 14523456789[...]093357 firstname.lastname@example.org
ai3gate.cs.ait.ac.th 1024 37 14523456789[...]093357Note that the syntax of the file has slightly changed. Here ai3gate.cs.ait.ac.th is the host you plan to connect to. If you define a fully qualified name in the file known.hosts, you then have to use a fully qualified name to make the connection.
As a result, when you are trying to use some programs that check the variable DISPLAY to modify their behaviour (for example emacs) they will hang.
Note: (this may be linked to our local configuration) we are linked to a Novell server where my user name is ON (upper case), so SSH was offering me to connect to the remote machine using that as user name, while the account on Unix machine is on (lower case), I did lost quite some time on this stupid mistake, searching for some tricky protocol error.
|Contact us: Olivier Nicole||Last update: Nov 2001|