Slashdot Mirror

← Back to Stories (view on slashdot.org)

Windows Server 2019 Officially Supports OpenSSH For the First Time (neowin.net)

Posted by ryuzaki0 on from the about-time dept.

Microsoft said in 2015 that it would build OpenSSH, a set of utilities that allow clients and servers to connect securely, into Windows, while also making contributions to its development. Neowin: Since then, the company has delivered on that promise in recent releases of Windows 10, being introduced as a feature-on-demand in version 1803. However, Windows Server hadn't received the feature until now, at least not in an officially supported way -- Windows Server version 1709 included it as a pre-release feature. But that's finally changed, as Microsoft this week revealed that Windows Server 2019, which was made available (again) in November, includes OpenSSH as a supported feature.

5 of 129 comments (clear)

  1. Interesting by guruevi · · Score: 2, Interesting

    The question is: what version, does it have Microsoft-specific extension and what shell do you end up getting (Bash would be nice).

    The problem will be when (not if) Microsoft refuses to patch just to point out how 'insecure' Open is.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
    1. Re:Interesting by currently_awake · · Score: 3, Interesting

      The next step is removing the underlying OS from windows and loading in linux underneath a Windows command shell (kindof like what Apple did with MacOS and freebsd). That would give them a dominant share in the growing linux market at little cost, and offload most of the maintenance costs onto the open source groups.

    2. Re:Interesting by mejustme · · Score: 3, Interesting

      I have it on a 2012 R2 to create reverse tunnels, the shell you get is the normal cmd.exe.

      What happens when you attempt to run a GUI application? E.g., notepad.exe?

    3. Re:Interesting by ourlovecanlastforeve · · Score: 5, Interesting

      You joke but this is actually where Microsoft is going.

      I remember back in 2005-ish there was an ashcan mag published by former Microsoft employees you could subscribe to for ~$50/year that contained internal memos, emails, etc. and one of the big email threads that was kicked around back then is that Microsoft's future game was to get out of selling Windows as a software product and turn their OS platform into a software-as-a-service model where your hardware would only have a RTOS-based microkernel and the OS would be streamed to you on demand much like the Terminal Services model.

      The backend services for that model were meant to run on Linux servers. The end game objective of moving into supporting Linux and contributing code to open source projects is for Microsoft to take over the open source community as a whole by first contributing code, then becoming an asset to the community, then financing development of open source projects. Then when the open source projects can no longer function without Microsoft's funding they would enact a hostile takeover of the open source community by withholding financing unless the community bends to Microsoft's whims.

      It's very much a "if you can't beat them with a better product, infiltrate and wreck their shit" scenario.

  2. Advantage over RDP? by nuckfuts · · Score: 3, Interesting

    As a Unix / OpenBSD fan, I think this is kinda cool, but unless one needs to login to Windows from a Unix box, what would be the advantage of this over RDP? With RDP I can access graphical features, easily map local resources such as drives and printers, connect through a TS gateway, etc.