-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Should New-PSSession using SSH accept user@hostname? #6284
Copy link
Copy link
Closed
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdlets-Corecmdlets in the Microsoft.PowerShell.Core modulecmdlets in the Microsoft.PowerShell.Core moduleWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdlets-Corecmdlets in the Microsoft.PowerShell.Core modulecmdlets in the Microsoft.PowerShell.Core moduleWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently,
New-PSSessionhas a parameter set to use-Hostnameand-Usernameto indicate SSHTransport is being used (instead of-ComputerNameand-Credential). SSH users are probably more familiar and comfortable withssh user@hostname, so it seems we should supportNew-PSSession -Hostname user@hostname(unfortunately, it would be a breaking change to default to-Hostnameinstead of-Computernameto support this as a positional parameter)cc @PaulHigin @joeyaiello