18 ms·
Windows can have a neat-o shell all they want but when you open powershell on a windows computer you still get the following when you try to ssh... so, not real
by tgarma1234 10y ago
Windows can have a neat-o shell all they want but when you open powershell on a windows computer you still get the following when you try to ssh... so, not really seeing the point here:
ssh : The term 'ssh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
- jaykru 10y agosee: https://github.com/PowerShell/Win32-OpenSSH https://github.com/PowerShell/Win32-OpenSSH. ssh is coming, likely in an official capacity in the future (this is an official MS group on github)
- hoverbear 10y agoWow your comment is bafflingly low quality and stupid. Perhaps you shouldn't have submitted it.
- guitarbill 10y agohe's not wrong though. ssh is the quickest way of accessing remove machines, not to mention secure (i have never seen remote desktop done with priv/pub key in practice). it also makes automation and transferring files easy. putty is terrible compared to ssh on linux. what i would have given for good ssh on windows back when i was still doing C#...
- jodrellblank 10y agohe's not wrong though. ssh is the quickest way of accessing remove machines Invoke-Command -ComputerName $ListOfComputers -Command {#code...}
- guitarbill 10y agoyes, yes, well done. how does this work with public/private keys again?
- jodrellblank 10y agoLike this: http://www.hurryupandwait.io/blog/certificate-password-less-based-authentication-in-winrm http://www.hurryupandwait.io/blog/certificate-password-less-... ... probably.