If you have any comments or questions about this documentation, please e-mail winathena-suggestions

News

You might find more up-to-date information at:

• http://www.globalnews.com/~bgould/sshd.html
• http://v.iki.fi/nt-ssh.html

Intro

Someone has a port of ssh 1.2.26 based in cygwin32 beta 19. All of the binaries are compiled. I have tested ssh, sshd, scp, and ssh-keygen. Port forwarding works. I imagine X11 forwarding works as well.

Note that the cygwin32 beta 19 is not necessarily very stable. Performance may not be the greatest either.

The guy who released the port also gives the diffs he used, so we should be able to rebuild/enhance the software ourselves if we want to.

Required Files

I packaged up the required files to make sshd work in ssh-port.zip

If you do not want to pick up the ssh-port.zip files as described at the top, you can pick up these packages yourself:

• ssh binaries for Win32
  If you do not want to get the ssh binaries from the ssh-port.zip file, you can get them directly from the author's distribution point. If you want to know more about the author and the port (including seeing the diffs to ssh), you can see the his homepage.
• cygwinb19.dll
  If you do not get this from the ss-port.zip file, you may want to use the port's author's updated DLL, which is included in a gziped tarfile of his. Looking at his diffs, I think you should be able to use the standard one from the cygwin32 b19 disttribution.
• sh.exe
  If you do not get it from the ssh-port.zip file, you'll have to install the cygwin32 b19 distribution to get this.

Setting up sshd

• unzip ssh-port.zip into the root of your C:\ drive. This will create the directory structure that cygwin32 needs, including having a /bin/sh, and /etc and /tmp directories.
• put c:\bin;c:\bin\ssh in your path
• add the following to your environement: CYGWIN32=tty (This is crucial!)
• from the shell, execute: mkpasswd -l > \etc\passwd
• from the shell, execute: ssh-keygen1 -f /etc/ssh_host_key
• in User Manager:
  • create group "LogonUser Group" and add people you want to be able to ssh in
  • go to Policies | Account Rights menu item
  • click "Show Advanced User Rights"
  • give "LogonUser Group" the following rights:
    • Act as part of the operating system
    • Increase quotas
    • Replace a process level token
• now you should just be able to run c:\bin\ssh\sshd1
  (Note: To set up sshd as a service, you may be able to use SRVANY from the Windows NT resource kit. If you do so, make sure that sshd1 is running under the correct environment (i.e., CYGWIN32 environment variable is set to tty).)

Using ssh

You cannot log in using your domain credentials. The sshd code does not support that (though it should be fairly straightforward to patch up the sshd code to support that). You need to login using a local account.

It takes a little while to log in. You will not see a prompt when you log in (unless you set up the appropriate dotfiles...) To verify that you got a shell, type "set"...It takes a few seconds for the shell to get started up. The tty stuff is pretty primitive... You will not be able to run cmd properly (though you can do cmd /c dir, etc.).

If you need to kill sshd, you will need to use the task manager. (You can end up with orphaned processes, I think....try not to start processes remotely if you can help it.)

If logging in is not working, you can try running sshd in debug mode, where it accepts only one connection then quits:
sshd1 -d