This project is _not_ about bringing UNIX to Windows. It is about bringing the open ssh protocol to Windows. As a daily UNIX and Windows user in an enterprise environment, I can say that a fully integrated sshd is a welcomed addition. I have written and maintained many WinRM interop ruby gems and cannot wait until we can deprecate them in favor of a better and sane remote she'll implementation. This is a real milestone, keep up the great work.<p>As for Cygwin sshd, it does work if posix is the order of the day but if you need a reliable terminal (for things like powershell) that scales to hundreds of servers and many admins Cygwin simply fails the test. Clunky domain authentication, private key auth is a joke, powershell only works sometimes (thanks PTY), network tokens are non-existent, etc. the list goes on and on.
See also <a href="https://github.com/PowerShell/Win32-OpenSSH/wiki/ssh.exe-examples" rel="nofollow">https://github.com/PowerShell/Win32-OpenSSH/wiki/ssh.exe-exa...</a> once you've got it running. To work around a bug, you'll currently need to run `powershell -File -`<p>It's still way too early to us as a daily driver - lots of small bugs - but nevertheless interesting.
So once you've done this and you SSH in to the Windows box, I assume you just end up, basically, in a command window?<p>For example:<p><pre><code> $ ssh username@windows.example.com
...
C:\>
</code></pre>
Is that right?
Interesting that the build instructions refer to Cygwin. It's a bit surprising, I'd have expected something more native. What does this bring to the table that regular Cygwin OpenSSHd couldn't do 10 years ago?
Feature request: Domain group policy setting for authorized keys. Make some ssh key(s) authorized to logon as some domain user(s) for every machine in the domain.
You can already install OpenSSH for Windows without bothering with PowerShell. See <a href="http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-windows-10/" rel="nofollow">http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-w...</a>
Microsoft is going about the whole SSH thing in a very backwards way.<p>If all they did was make or back an official POSIX environment, all of this comes for free.<p>Insisting that PowerShell be the focal point for all these changes is just bizarre.<p>Just install msys2.
This is great news. @ Userify[1], we're looking forward to porting our shim to PowerShell asap.<p>1. <a href="https://userify.com" rel="nofollow">https://userify.com</a>