Deprecate SNMP Enabler for Windows

Please consider marking the SNMP Enabler for Windows tool as deprecated on its download information page. CIM data obtained via WMI queries is much richer and more secure than SNMP, and Microsoft moved its focus on Windows away from SNMP years ago. The product page could feature a link to the Remote Execution Enabler for PowerShell page and to something like an updated version of @adatole's SNMP vs WMI post.

Find more posts tagged with

sam

Best Practices

SNMP

npm

WMI

Status: None

Comments

frak

Last I looked at the Remote... for Powershell it was using deprecated crypo so not so secure. Stopped using it at that point. Was a convenient tool, though.

sturdyerde

Curious if you could be more specific about depcreated crypto with the Remote enabler tool for PowerShell. It's not perfect--it uses self-signed certs and might default to port 5895 instead of port 5986, but that's still encrypted. Either way, it still seems a far cry better for any Windows endpoints, no?

frak

It wasn't the self signed certs. It was the crypo used - had a bit of an issue when I realised as disallowed on our network. I went back to doing it by hand through Powershell. The tool was much easier, though. I don't recall what the algo was, but have not heard that it has been changed so not gone back to it. Check the crypto used on one of your machines that has recently been setup by the tool - I would love to know.

sturdyerde

Hmmm, interesting. If you have more detail, it would be a great read. I'm having a hard time thinking of any ways that this tool would be able to make use of a specific algorithm or cryptography suite for the WinRM listener unless it was actually specifying a weak cipher for the certificate itself.

Microsoft doesn't say much about WinRM security other than, "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/learn/remoting/winrmsecurity