THIS PROJECT IS DISCONTINUED.

An installer for a minimal installation of the Cygwin environment suitable for running an OpenSSH server on the Windows platform.

Project Activity

See All Activity >

Follow OpenSSH for Windows

OpenSSH for Windows Web Site

Other Useful Business Software
Paessler: Easy to Use With Enterprise Power. Free Trial Icon
Paessler: Easy to Use With Enterprise Power. Free Trial

A low-code dashboard makes monitoring intuitive for any admin, while scripting and custom sensors give experts full control.

You shouldn't have to choose between a monitoring tool that's easy to use and one that's powerful enough for a complex environment. PRTG's low-code interface lets any admin build dashboards, set alerts and monitor devices without scripting, while custom sensors and full API access are there when your team needs deeper control. One platform, no compromise. Download a free 30-day trial now.
Get Free Download
Rate This Project
Login To Rate This Project

User Ratings

★★★★★
★★★★
★★★
★★
★
4
1
2
1
17
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 2 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 2 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 2 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5

User Reviews

  • This project seems outdated. One may think of using this one instead: @github.com/PowerShell/Win32-OpenSSH/releases/
  • It overwrites PATH!
  • Dangerous piece of junk. If it wiped your path variable the following registry entry has the original one: HKEY_LOCAL_MACHINE\SYSTEM\XXX\Control\Session Manager\Environment\Path where XXX is ControlSet001 or ControlSet002 or Current ControlSet. see superuser.com search for "deleted-path-environment-variable-how-to-restore"
  • It destroys PATH variable.
  • ERMAHGERD! Installing this package overwrites the PATH variable in Windows...! Anyone who knows enough about command line use to install OpenSSH on a Windows machine really SHOULD know enough about the PATH variable to adjust for this problem. I admit that I didn't read the reviews first, and found myself in the same boat. Easy fix, though, as I've had to play with the PATH in Windows in the past, and Google can quickly tell me what it should be if I forget. The simplest solution is to copy the current PATH, install the program, then add the original PATH back in using a simple ; between the two entries. Problem solved. My Windows PATH looks like this, now: C:\Program Files (x86)\OpenSSH\bin;C:\WINDOWS\System32 Now I can continue to use my Windows command line like I did before, but I can also use OpenSSH with equal ease, and I'm very thankful, as I can now access my Linux server(s) from my work computer, which has to be Windows (I would rather have Linux, but...) Need other things added to the PATH variable? Remember to use the ; between entries. If this is too difficult, install WinSCP instead.You'll still have to know how to use the command line, but it doesn't mess with the PATH variable.
Read more reviews >

Additional Project Details

Registered

2004-03-06