Technically it is SSH. You won't use Powershell cmdlets in the session, you will use shell commands native to the remote system you've connected to.
> Technically it is SSH. You won't use Powershell cmdlets in the session, you will use shell commands native to the remote system you've connected to.
In terms of how remote shell access gets used for interoperability with other non-Windows systems, the existing Windows-proprietary remote connections were not useful. They were for Windows-to-Windows sessions. The rest of the world has used SSH for a long, long time.
For Windows, the only major operating system that stubbornly refused to admit anything other than itself existed in production environments for decades, to finally recognize that it needs to learn to play well with others, is a non-trivial advance in interoperability for everybody.
Ballmer's myopic view that everything but Windows is either a toy (Apple) or a cancer (Linux) made Windows a laughingstock among serious mixed-environment system admins and developers for the last couple of decades. We dealt with it only because we HAD to for certain business applications. We put up with third-party bolt-ons because it was the only way to get real work done.
SSH is the network login communications standard everywhere except Windows. Finally, Windows will start being less of a pain in the ass to everyone who isn't an insulated Windows-only shop.