4 ms·
"The listener that is created when you enable PowerShell Remoting is over HTTP. You are able also to configure WinRM over HTTPS" Doesn't seem like a good idea
by tyingq 8y ago
"The listener that is created when you enable PowerShell Remoting is over HTTP. You are able also to configure WinRM over HTTPS"
Doesn't seem like a good idea to default to plaintext.
- 13of40 8y agoIt's not plain text. The traffic is still encrypted by winrm.
- tyingq 8y agoAhh. Would be a good note in that area of the article.
- newman314 8y agoI was curious about the details and did some digging. "Regardless of the transport protocol used (HTTP or HTTPS), PowerShell Remoting always encrypts all communication after initial authentication with a per-session AES-256 symmetric key." https://docs.microsoft.com/en-us/powershell/scripting/setup/winrmsecurity?view=powershell-6#encryption-and-transport-protocols https://docs.microsoft.com/en-us/powershell/scripting/setup/...
- genericid 8y agoThen what's the point of using HTTPS? Heating the room?
- jodrellblank 8y agoSee my other comment, but a) it encrypts more of the packets, b) helps with validating correct server, c) encrypts even if you end up authenticating without Kerberos somehow.
- srinathgs 8y agoWhen using HTTP for remoting, headers are not encrypted. But body is always encrypted when using NTLM, CredSSP or Kerberos - the GSSAPI supported protocols. If user doesn't want to use these and opts for basic auth or some other protocol that doesn't have encryption specified, https is useful.
- jodrellblank 8y agoIt's typical Microsoft engineering, and I say that as a frequent defender of powershell here. It's encrypted, except when it isn't, except on Tuesdays when it is. https://www.reddit.com/r/PowerShell/comments/97oxox/comment/e4blfgj https://www.reddit.com/r/PowerShell/comments/97oxox/comment/... "Just an FYI not all psremoting traffic is encrypted when using http. Message encryption is done using the authenticated context which varies based on what auth was actually used. For example Basic auth has no authenticated context in SSPI so has no encryption. NTLM (fallback if kerb is not available) is next to useless as it is based on RC4 which is considered broken today. Kerberos should be using AES if configured correctly but older environment may have older insecure algorithms set up if the config is mismanaged on the domain level. CredSSP uses the TLS context that is set up in the auth so is similar to using HTTPS. When using https you not only get a more consistent and secure encryption mechanism on all auth methods. You also get encryption on the whole TCP packet that is sent to the client, whereas http message only encryption encrypts the message body." And "My understanding of the issue is that WinRM can do more than just Powershell Remoting (for example there are also Python libraries that run on Linux machines to interface with WinRM which I'm assuming do something different to PS remoting since PS is not native/required on those platforms). So if you are doing ONLY Powershell Remoting you're probably fine with HTTP, but if you're doing anything else then it could be exposed via HTTP WinRM. So HTTPS is still recommended. tl;dr - All Powershell Remoting is WinRM, not all WinRM traffic is PS Remoting." https://www.reddit.com/r/sysadmin/comments/5vph9l/winrm_encryption_question_xpost_from_rpowershell/ https://www.reddit.com/r/sysadmin/comments/5vph9l/winrm_encr... And I think lots of people couldn't get a straight answer on this and it came up on the recent MCP Insider AMA. First 3 minutes of video 2 "it's secure, use it [...] tell 'em Jeffrey Snover told you, go do it". "Also, for more information on security when remoting read the powershell.org free e-book, Secrets of PowerShell Remoting.*" https://www.reddit.com/r/PowerShell/comments/34yzgt/comment/cqzj4l2 https://www.reddit.com/r/PowerShell/comments/34yzgt/comment/...
- userbinator 8y agoIt's typical Microsoft engineering What surprises me the most is they could've used the existing (also quite over-engineered, but existing nonetheless) MSRPC infrastructure for this, like what psexec does, but chose to use a completely different set of technologies once again.