Indications that Chocolatey is locked down

# System's version is less than vendor's current (Chocolatey v0.10.15)
0+000+00[LAX-WEB005]: PS C:\Users\testadmin\Documents> choco source
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28

# Server unable to reach chocolatey.org
[LAX-WEB005]: PS C:\Users\testadmin\Documents> wget https://chocolatey.org/api/v2/
The request was aborted: Could not create SSL/TLS secure channel.
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest],WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

What to do?

When a system has outbound firewall access control lists (ACL’s) blocking HTTP outbound as shown above, one may assume that it’s as intended. Proper protocol when attempting to make changes to these sorts of systems would be to obtain authorization from systems owner. Once approved, one may proceed to apply the knowledge from this documentation (https:// docs.chocolatey.org/en-us/features/host-packages) to administer this system.

Note: when I have time, I may provide practical examples on how to deploy & admin private Chocolatey repos…

Leave a Reply

Your email address will not be published. Required fields are marked *