Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Publishes OpenSSH For Windows Code (msdn.com)

Posted by Soulskill on from the go-break-it-before-somebody-else-does dept.

An anonymous reader writes: Microsoft has published early source code for its OpenSSH-for-Windows port for developers to pick apart and improve. In a blog post on Monday, Steve Lee – the PowerShell team's principal software engineer manager – said Redmond has finished early work on a Windows port of OpenSSH 7.1, built in a joint-effort with NoMachine. Their rough roadmap from here: 1) Leverage Windows crypto APIs instead of OpenSSL/LibreSSL and run as Windows Service. 2) Address POSIX compatibility concerns. 3) Stabilize the code and address reported issues. 4) Production quality release.

4 of 164 comments (clear)

  1. Re:They already are by ralphsiegler · · Score: 3, Informative

    very funny, windows only does posix 1 which is 1990. you must be confusing window's level of posix compliance with something that is actually useful.

  2. Re:"to pick apart and improve" by vux984 · · Score: 4, Informative

    How would this improve it?

    Maybe ... key management; using the windows platform key stores. Integration with active directory etc.

  3. Re:Will it tunnel applications? by Minwee · · Score: 5, Informative

    If I can expect a windows machine to have an ssh daemon capable of tunneling the RDP port to my machine locally, I would be gaining a lot. Such as no longer exposing RDP directly to the client via a VPN.

    ssh -L 3389:127.0.0.1:3389 myusername@somewindowsserver

    Run that, and then try to connect to remote desktop on your local machine. It works with any proper SSH server, including Cygwin. Do you have any other requests?

  4. Re: Where is bash? by Anonymous Coward · · Score: 2, Informative

    Powershell supports using COM object APIs directly, so of course the design is going to look very different to bash.