News for hackers. Stuff that matters.
Re:PowerShell Remoting by 13of40 on Tuesday August 21, 2018 @08:31PM (#17815136)
It's not plain text. The traffic is still encrypted by winrm.
Re:PowerShell Remoting by tyingq on Tuesday August 21, 2018 @08:55PM (#17815285)
Ahh. Would be a good note in that area of the article.
Re:PowerShell Remoting by newman314 on Tuesday August 21, 2018 @08:58PM (#17815305)
I 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/...

Re:PowerShell Remoting by genericid on Tuesday August 21, 2018 @09:34PM (#17815521)
Then what's the point of using HTTPS? Heating the room?
Re:PowerShell Remoting by jodrellblank on Tuesday August 21, 2018 @09:41PM (#17815556)
See 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.
Re:PowerShell Remoting by srinathgs on Tuesday August 21, 2018 @10:40PM (#17815838)
When 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.