$Id: README.NT,v 1.3 2000/01/06 22:42:08 cxh Exp $
This is a partial port of SSH to Windows NT, which provides a
command line versions of ssh and scp for use with cvs.
This port is not meant to provide a fully functional ssh shell.


Most of the changes are based Gordon Chaffee's ssh-1.2.14-win port at
	http://bmrc.berkeley.edu/people/chaffee/winntutil.html#sshnt

To build on NT with Visual C++:
1. Download the original sources from
ftp://ftp.cs.hut.fi/pub/ssh/ssh-1.2.27.tar.gz
and untar them

2. Patch as follows
  cd ssh-1.2.27
  patch -p1 < ../ssh-1.2.27-win.patch

3. edit makefile.vc, zlib1.0.4\makefile.vc, and
gmp-1.3.2\makefile.vc to change TOOLS32 to point to the compiler directory

2. Then, run
   nmake -f makefile.vc

Gordon Chaffee's original instructions said:
--start--
  This version is not a full terminal. It allows you to run commands
 such as ssh remote_machine -l chaffee ls, and it even lets you log
 into other machines interactively, but it gives you only dumb terminal
 capabilities. For a version that might have full capabilities, try
 this port of ssh
 (http://www.geocities.com/SiliconValley/Bay/1692/ssh-index.html) or
 TTSSH (http://www.zip.com.au/~roca/ttssh.html).

 You'll need to create a c:\ssh\etc directory to keep your ssh_config,
 ssh_host_key, and ssh_host_key.pub in. You need to generate the keys
 on your Unix box with ssh-keygen as I haven't fixed it yet. It does
 get compiled, but it doesn't work. Next, make sure your HOME
 environment variable is set. One NT, this can be done via the Control
 Panel->System. You can also do it on the command line (or in
 autoexec.bat) using set HOME=c:\users\yourname. This works on NT and
 Windows 95. Finally, create a %HOME%\.ssh directory like you would
 under Unix. Put your identity and identity.pub files in there as well
 as any others you might use. With that, things should work. If you
 make a copy of ssh.exe to sshc.exe, it will automatically run with
 compression on. I find this useful when running with cvs.
--end--

This port has the following changes between ssh-1.2.14-win

* Upgraded to use ssh-1.2.27
* Upgraded to use ssh-1.2.26
* .rhosts RSA Authentication now works (see cvsssh/README.txt)


I chose not to use ssh-1.2.22-Win32-Beta1-src for the following reasons

* It is based on ssh-1.2.22, which may have security holes
* It uses Cygwin, which is not secure in a multi user environment
http://sourceware.cygnus.com/cygwin/faq/faq_8.html#SEC62
says
> How secure is Cygwin in a multi-user environment?
> 
> Cygwin is not secure in a multi-user environment. For example if you
> have a long running daemon such as "inetd" running as admin while
> ordinary users are logged in, or if you have a user logged in remotely
> while another user is logged into the console, one cygwin client can
> trick another into running code for it. In this way one user may gain
> the priveledge of another cygwin program running on the machine. This
> is because cygwin has shared state that is accessible by all
> processes.
>
> (Thanks to Tim Newsham (newsham@lava.net) for this explanation). 

BUGS
* gmp-2.0.2-ssh-2 does not compile with Microsoft Visual C++ 6.0
The problem is that the assembler files in gmp-2.0.2-ssh-2/mpn/x86/pentium
are not compiling.