SSH and related (open) protocols in Windows PowerShell - by Real McCoy

Status : 

 


30
5
Sign in
to vote
ID 786397 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 5/6/2013 12:07:19 AM
Duplicates 715414 Access Restriction Public

Description



[Redirected from http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/f70168bf-f575-47c7-b889-3c38dd6a776a]


I guess the lack of out-of-the-box support for the open protocols, such as; SSH and SFTP in Windows shells is one the main reason the PHP, Ruby and Python developers don't feel nativity in Windows ecosystem.

 

Windows Azure supports SSH, so what's stopping Windows PowerShell and Command Prompt teams to implement these proven and massively adopted protocols in their commands bucket? Is it due to any legal (open source licensing) issue?

 

Since TFS team is  pushing git support in upcoming release of Visual Studio, it would be nice if Windows guys implement SSH and SFTP in Windows vNext. 
Sign in to post a comment.
Posted by Joel 'Jaykul' Bennett on 2/17/2014 at 8:25 PM
First of all, no shell "supports" ssh -- they just support running applications. PowerShell does that.

Secondly: how is SSH any more "open" than WS-Management? Maybe you meant to emphasize that it's older and more popular.

Having said that: other operating systems ship applications to support ssh in their default distributions.
There are lots of binary implementations of SSH for Windows, it would be nice if Windows shipped with a basic command-line ssh client IN THE BOX.

Posted by Trevor Sullivan [MVP] on 8/14/2013 at 1:28 PM
PowerShell supports remote sessions over the Distributed Management Task Force's (DMTF) WS-Management standard. The WS-Management standard is implemented via the Windows Remote Management (WinRM) service. PowerShell Remoting allows developers to return rich, arbitrary .NET objects from the remote session to the client session.
Posted by Real McCoy on 5/9/2013 at 11:42 PM
@Oisin Grehan,


If you haven't realized that, the idea of this "suggestion" really is to have "native" support of SSH/SCP/SFTP in both Windows CLIs. Picking on works is really not necessary. Its helping nobody.

Believe it or not, but many people would agree that the native SSH support is better than installing a third shell systems such as CigWin, MinGw and PuttY just for connecting to your hosting service (for perhaps restarting your webserver!) in Windows OS.
Posted by Oisín Grehan on 5/9/2013 at 6:15 AM
Why is it "fending off developers?" Last time I checked, Windows didn't block the installation of SSH tools. Being a console application, powershell doesn't need any special support for SSH. It works right now.