6 ms·
Microsoft has a real hole in their stack in my opinion... So on Linux you have SSH (for shell) and X11 Forwarding/VNC for GUI remoting. On Windows you have RD
by Someone1234 12y ago
Microsoft has a real hole in their stack in my opinion...
So on Linux you have SSH (for shell) and X11 Forwarding/VNC for GUI remoting.
On Windows you have RDP for GUI and nothing for remote shell.
Now, I know what you're going to say, "WMI" but WMI was never designed for use over the internet. You have to forward two fixed ports and a dynamic range (shudder). Plus it isn't security hardened either by design or through fire.
VPN you say? In theory yes. But the reality on the ground is that for most SMBs they're still using RDP or SSH directly to manage Windows/Linux servers, and if Windows wants to compete (and they are dropping RDP) they need to have an "answer" to SSH.
Essentially they need to take whatever WMI is, wrap it into a secure protocol, and bind it to just a single port, then harden the heck out of whatever process directly runs on that port (before you hit the WMI interface itself).
Or alternatively write an SSH server (literally), and after login redirect input to a Powershell process. Nobody would complain about that (plus free SFTP support!).
PS - I'm totally going to get attacked by "VPN purists" here. But really everyone knows that SSH and RDP is extremely common for SMBs/private individuals. Let's quit pretending that it is not and support the client that actually exists, not the client you wished existed.
- sixothree 12y ago> We are improving remote manageability via PowerShell with Desired State Configuration as well as remote file transfer, remote script authoring and remote debugging Is PowerShell not what you're looking for, or is it not implemented similar to SSH?
- Someone1234 12y agoRemote Powershell exists, but you don't have a great deal of control over the Powershell interface (like you would with an SSH daemon), if you want to "opt-in" users one by one for remote Powershell, well, you cannot. Also setting it up to work over the internet securely is, a touch complicated: http://blogs.technet.com/b/askpfeplat/archive/2012/09/17/want-remote-powershell-management-from-your-browser-see-how-powershell-web-access-in-windows-server-2012-may-help.aspx http://blogs.technet.com/b/askpfeplat/archive/2012/09/17/wan... It is a cool party trick that it can work via a web-browser and IIS. But if that's what it takes to make Powershell remoting secure without a VPN then it isn't workable.
- UK-AL 12y agoJust getting it to work with shell, and no web browser access is a lot simpler than that. A few lines. See my reply at https://news.ycombinator.com/item?id=9343060 https://news.ycombinator.com/item?id=9343060
- simonjgreen 12y agoSSH access to PowerShell would be a game changer IMHO for Microsoft. Also, have you seen this? http://www.powershellserver.com/download/ http://www.powershellserver.com/download/
- UK-AL 12y agoYou can have remote access to powershell...
- freehunter 12y agoI don't know if it exists the other way around or not, but it would be really nice if Windows had a built in SSH client as well. I can't tell you how many times I've been working on a client's Windows Server machine and needed to remote into a Linux server, but neither I nor they had access to download Putty.
- tracker1 12y agoAgreed... I generally wind up with git extensions everywhere which includes most of the gnu tools including ssh. The only down side is that ssh via windows command shell, even in conemu doesn't do ansi/drawing properly... never really investigated as I just try to avoid it all.
- basch 12y agohttp://www.mls-software.com/opensshd.html http://www.mls-software.com/opensshd.html
- motoboi 12y agoAre you aware that is already possible to remote login into a powershell session without any add-on on windows server? Just use Enter-PsSession -computername
- deevus 12y agoPowerShell Server "gives users the power to securely manage Windows remotely through PowerShell from any standard SSH client"
- akoeplinger 12y agoPowerShell web access might be a good alternative: http://blogs.technet.com/b/askperf/archive/2012/11/05/windows-8-windows-server-2012-windows-powershell-web-access.aspx http://blogs.technet.com/b/askperf/archive/2012/11/05/window...
- UK-AL 12y agoYou don't need this. You just need Enter-PSSession [ipaddress], which allows you to interact with it like ssh. You need to enable powershell remoting first though.
- akoeplinger 12y agoYes, but only if both PCs are in the same domain. Getting PowerShell remoting to work in other environments requires a lot of configuration.
- UK-AL 12y agoThat's not true. I had it working over the internet, separate domains with public/private certs fairly easily.
- akoeplinger 12y agoI'd be interested in how you set it up, can you maybe share it somewhere? Guides like https://wprogramming.wordpress.com/2011/07/11/remote-pssession-over-ssl/ https://wprogramming.wordpress.com/2011/07/11/remote-pssessi... don't seem "fairly easy" to me (that's why I said it requires a lot more configuration compared to Enter-PSSession when both parties are in the same domain).
- UK-AL 12y agoThere's a lot of waffle in that. If you actually look at the commands his asking you to enter, it isn't that much. It's essentially, Enable-PSRemoting And commands 1 to 3 in the following guide after Enable-PSRemoting. Try to ignore the waffle. You probably do want to to disable HTTP though. http://www.sirchristian.net/blog/2013/03/11/using-powershell-remoting-over-the-internet-for-one-click-build-and-deploy/ http://www.sirchristian.net/blog/2013/03/11/using-powershell... Trying to get SSH to work with certs can involve just as much or more stuff than that. Maybe i'll write a super simple guide, just listing the bare commands, since the documentation/tutorials for powershell seem non-existent despite being pretty powerful..
- UK-AL 12y agohttp://ss64.com/ps/enter-pssession.html http://ss64.com/ps/enter-pssession.html
- darrenkopp 12y agoI'm not a ssh expert (I live in the MS world), but powershell remote sessions (PSSession) seems like what you are talking about here... it's like running in a powershell window on a remote machine.
- emn13 12y agoI'm not too confident powershell is really good enough to compete with the ancient unix shell. I've tried using it to automate windows machines, but it's certainly not a smooth experience. Part of that is the lack of a history of automation - basic things to do with processes and I/O are kind of schizophrenic. All of the basics are clearly unix inspired (standard streams, processes, redirection - this is all unix-like), but many windows tools use different conventions to exchange data and control channels - powershell has a real object model. In principle powershell's richer object model is a boon to automation - it's so much easier not to make mistakes if you don't need to massage your data through lots of slightly different text-based hacks, but the object model just isn't nearly pervasive enough. Sometimes you still need plain text/binary streams, and the transition isn't great. More fundamentally, the object model isn't well thought out - it's built on .NET, but that's clearly a single-process focused world view, and for a inter-process management tool, that poses problems. Even if sending objects between processes would work smoothly, there's the issue that objects don't compose or reflect as smoothly as text. It's hard to put your finger on, but for example, you can use things like regex's to do fairly fancy pattern matching on strings, and the equivalent for objects just isn't there in powershell. As a result, things work great if you're doing something that the underlying processes "want" you to do - but if you're trying to hack around some limitation, or try something novel, it's much more painful than in bash. I think it's also worth mentioning some practical problems: Powershell is really slow and heavy. You can cheaply pipe and juggle data in a unix shell, but by doing that in powershell I've seen machines grind to a halt. A fresh powershell instance has a working set of 100MB on my machine; bash: 5MB. That's a problem. Startup time, similarly, is slow. This isn't a problem if you're working purely interactively - no human is going to notice an extra 10ms here or there, but in scripting, you can easily start so many processes that the difference becomes very noticable. Powershell isn't terrible, but it just doesn't work as well as the unix shell, despite all the warts that has. Maybe some day everything will speak powershell, and it'll faster, smaller, and have a better story concerning pattern matching, but right now it's relatively ineffective compared to a plain unix shell, in my experience (which is windows centric).
- useerup 12y agoYou are ignoring Windows Remote Management, Microsofts implementation of the WBEM standard protocol for remote management of devices. https://msdn.microsoft.com/en-us/library/aa384426(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/aa384426(v=vs.85).a... "Windows Remote Management (WinRM) is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems, from different vendors, to interoperate. The WS-Management protocol specification provides a common way for systems to access and exchange management information across an IT infrastructure. WinRM and Intelligent Platform Management Interface (IPMI), along with the Event Collector are components of the Windows Hardware Management features."
- anoother 12y agoHave you ever tried using wsman? It is not fun. And, being SOAP-based, it's certainly nothing like a command-line. But most of all, it's not fun.
- algorithmsRcool 12y agoI've used winrm for some VM config scripts. The ps script would clone a VM from a base image, boot it, then remote into it to config network and other things. It was a bit arcane to set up but mainly it was slow, like, really slow. All the SOAP serialization is terrible for performance but it is flexible and it did work.
- nailer 12y agohttp://www.powershellserver.com/ http://www.powershellserver.com/ MS should really include something like this in Windows. Hell, I (or you) should find the time and write it ourselves, node.js has great TLS support and has a Windows port.
- amithgeorge 12y agoPowershell currently only runs on Windows. One can't use powershell remoting from a Mac OS or *nix machine. Until someone adds non-windows support for Powershell, they need to have a built-in ssh server that opens powershell as the shell. Btw, even if that does happen, it's still difficult to use PS. Any errors that occur in the remote environment get displayed as XML blobs on the client :(