Microsoft bringing SSH to Windows and PowerShell
Peter Bright / Ars Technica :
Context & Ripple Effects
In mid-2015, Windows shipped without a built-in SSH client or server, leaving administrators to bolt on third-party tools or work from Linux machines to manage remote systems. Microsoft's decision to bring SSH into Windows and PowerShell put the company's own shell at the center of that gap — and set up the cross-platform turn that followed, when PowerShell was open sourced and ported to Linux and OS X.
The move reads as the opening data point of a decade-long arc: from SSH support to the native OpenSSH client and server beta in Windows 10, through continued WSL investment, to the Linux-like Coreutils utilities and WSL containers announced for Windows developer tooling. Each step chipped away at the command-line divide between Windows and Unix-adjacent environments.
First-order effects
- Windows administrators gain a native path for encrypted remote management of servers and network gear, removing the dependence on third-party SSH clients for day-to-day operations.
Second-order effects
- SSH inside PowerShell makes the shell credible beyond Windows-only shops, foreshadowing its later open sourcing and availability on Linux and OS X.
Third-order effects
- If the pattern holds, Windows consolidates as a first-class platform for Unix-style development workflows — the endpoint visible in today's Coreutils, WSL containers, and Intelligent Terminal announcements.
The trend: Microsoft has spent a decade converging Windows with Unix command-line ecosystems, moving from adding SSH to shipping Linux-native tooling inside Windows itself.