Re:Microsoft Adds an OpenSSH Client to Windows 10
by joeyaiello on Tuesday December 12, 2017 @11:08PM
(#15911952)
It drops into cmd, but it is configurable (and there's actually a Chocolatey community package for it that I believe prompts you for which default shell you want at install-time).
With PowerShell Core 6, we also support PowerShell Remoting Protocol (PSRP) over SSH as a transport, which means that you can do stuff like New-PSSession and Enter-PSSession without WinRM. (PowerShell just gets registered as a "subsystem" of sshd, same thing sftp-server does.) You can check that out here: https://github.com/powershell/powershell/tree/master/demos/S...
Re:Microsoft Adds an OpenSSH Client to Windows 10
by nailer on Wednesday December 13, 2017 @11:04AM
(#15915071)
That's really odd. Are you going to fix this before the final release?
Re:Microsoft Adds an OpenSSH Client to Windows 10
by flamtap on Tuesday December 12, 2017 @08:56PM
(#15911374)
Please say powershell... Please say powershell...
Re:Microsoft Adds an OpenSSH Client to Windows 10
by naikrovek on Tuesday December 12, 2017 @10:43PM
(#15911845)
cmd.exe, but it is probably configurable, and you can always just type 'powershell' to get it.
Re:Microsoft Adds an OpenSSH Client to Windows 10
by scott_karana on Tuesday December 12, 2017 @10:57PM
(#15911910)
Invoking via cmd is not comparable at all.
If it was direct to Powershell, you could pipe objects directly into remote cmdlets.
Re:Microsoft Adds an OpenSSH Client to Windows 10
by joeyaiello on Tuesday December 12, 2017 @11:17PM
(#15911990)
Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...
When I connect to a Windows box running an sshd, what exactly happens? Do I just get dropped into a command prompt or PowerShell session or what?