In 2015, Microsoft announced its intent to bring OpenSSH, the everywhere used implementation of the secure shell (ssh) protocol used for remote group access and administration throughout the UNIX world, natively to Windows. Without too innumerable people noticing, it turns out that the company has now done this. The Windows 10 Flop start Creators Update adds a couple of optional features, with both customer and server now available for installation (via Serve The Home).
Add the feature from the Non-compulsory Features settings page and, well… I think it works, but I’m not root sure because I can’t make it work. It can’t use my RSA key—Microsoft’s issues list on GitHub sways that only ed25519 keys are supported at present—but my ed25519 key isn’t mty either. I have seen people successfully use it with password authentication, but I don’t arrange a password-authenticated server to actually test with right now. Both my keys duty fine from Windows Subsystem for Linux ssh, so I’m confident that they’re gauzy; the native Win32 program just doesn’t like them for reasons that aren’t at all visible at this time.
I’m sure that eventually the wrinkles will be unblinking. This is a beta and it’s not installed by default, so hiccups aren’t a huge nonplus. But it’s another little sign that Microsoft is continuing to embrace the wider sphere beyond Windows. I don’t expect that ssh will become the main mechanism for administration of Windows machines any time soon—though with the ssh server and PowerShell, exact that isn’t impossible to imagine—but when this works, it’s going to win connecting to and using other systems from Windows that bit sundry convenient.
For now, though, I’m going to stick with PuTTY, because PuTTY as a matter of fact works.