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.

6 of 164 comments (clear)

  1. IT'S A TR...REPEAT! by Anonymous Coward · · Score: 0, Insightful

    Never liked any Star Wars movie. Didn't like Godfather. None of them. Never saw Goodfellas.

    1. Re:IT'S A TR...REPEAT! by KGIII · · Score: 3, Insightful

      What's funny is that if you look at source code today, probably even here on Slashdot, you'll find all sorts of Firefox-specific code in there. But we bemoan the days of needing to code for IE6 like the troubles are behind us.

      --
      "So long and thanks for all the fish."
  2. "to pick apart and improve" by UnknowingFool · · Score: 1, Insightful

    The question is for whom?

    1)Leverage Windows crypto APIs instead of OpenSSL/LibreSSL and run as Windows Service

    How would this improve it? How open is this crypto code? Yes, Open SSL/Libre SSL has had problems but if the Windows Crypto API is not open then they are replacing known problems for unknown problems.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  3. Where is bash? by nyet · · Score: 1, Insightful

    Pointless without bash.

    I''ll stick with cygwin, thanks.

    1. Re:Where is bash? by Anonymous Coward · · Score: 2, Insightful

      There is a hack-around way to get a remote command line but it's painfully obtuse and makes no sense.

      A hack-around? No, it's one single, built-in command:

      Enter-PSSession -ComputerName COMPUTER -Credential USER

      Instant access to an interactive shell on a server. To borrow the example from Microsoft's page, the following lists all the Powershell processes on the server and saves them into a file (also on the server):

      PS C:\Users\Anon> Enter-PSSession -Computer Server01
      [Server01]: PS C:\> Get-Process Powershell > C:\ps-test\Process.txt
      [Server01]: PS C:\> exit
      PS C:\Users\Anon>

      The only complication comes from the fact that remote access is turned off by default, so you have to configure your server to accept connections. But that is really how you want a server to be; secure by default.

  4. Re:This will end well by Anonymous Coward · · Score: 3, Insightful

    You're right. Windows would never do something so careless as sharing network passwords in an insecure manner.

    We all just need to get over it.