community.chocolatey.org
Open in
urlscan Pro
2606:4700:10::ac43:57e
Public Scan
URL:
https://community.chocolatey.org/packages/OpenSSL.Light/
Submission Tags: falconsandbox
Submission: On March 13 via api from US — Scanned from DE
Submission Tags: falconsandbox
Submission: On March 13 via api from US — Scanned from DE
Form analysis 4 forms found in the DOM
GET /packages
<form class="search-box search-d-submit " autocomplete="off" role="search" action="/packages" method="get">
<div class="flex-grow-1">
<input name="q" type="search" class="form-control search-input" id="searchQuery" placeholder="Search Packages" aria-label="Search Packages" value="" autofocus="">
<i class="fa-solid fa-magnifying-glass" aria-hidden="true"></i>
<span class="d-none d-md-flex search-key-container">
<span class="badge font-monospace text-bg-primary search-key">ctrl</span>
<span class="badge font-monospace text-bg-primary">k</span>
</span>
</div>
<button type="submit" aria-label="Search Packages" class="btn btn-outline-primary ms-2" title="Search Packages" value="">Search</button>
<button type="button" aria-label="Close search" class="btn btn-search-close btn-outline-primary ms-2"><i class="fa-solid fa-xmark" aria-hidden="true"></i></button>
<div class="search-help position-absolute w-100 top-100 start-0 end-0">
<div class="arrow-up position-absolute">
<div class="arrow-up-inner position-relative"></div>
</div>
<div class="card card-body text-bg-theme-elevation-1 mt-3 me-3 rounded d-md-flex flex-md-row justify-content-md-between border">
<p class="mb-md-0 small"><strong>id:searchValue</strong> search by id only</p>
<p class="mb-0 small"><strong>tag:searchValue</strong> search by tags</p>
</div>
</div>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" method="post">
<fieldset>
<input name="__RequestVerificationToken" type="hidden" value="s/+5m/Zvou8fg5O/fPAJbP/xQtD8wNHGzkwkL6SONpwqiHF/GU7zx1U/9byibYGdx6GQS2PXs/sgBsf0xDy3gQyXKoMfvIpyEV6pjvC7WBiHKukNpAwhS0YiubVxFpVfPc71rj924YCGyHqtI5kNKBgNXsks+vDNEOgmsJd4fP8=">
<button class="btn link-theme m-0 p-0" type="submit"><i class="fa-solid fa-right-from-bracket fa-flip-horizontal text-primary w-15-px text-center me-3"></i>Sign Out</button>
</fieldset>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" class="w-100 user-authenticated" method="post">
<fieldset class="nav-link">
<input name="__RequestVerificationToken" type="hidden" value="g+r/2SB3tFgtHFfFuMaYBa5v6Aj9BjZ0tQc8srE/EoX3Dfr9to3ouZ0wjTzod02nH7yJAxX4lLlFYolBRQDg+O5A0MheMw8pYMAMW5lQmS4Y15VP0kvbnV4jDovM595MECReVqm+xz5JwxsF5zrNJEWWp1dg7YRMgFNScO/rXUs=">
<button class="btn link-theme m-0 p-0" type="submit">Sign Out</button>
</fieldset>
</form>Name: mc-embedded-subscribe-form — POST //chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d
<form action="//chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate="">
<div class="row align-items-center justify-content-center">
<div class="col-md-auto text-center text-md-start">
<h3 class="mb-0">Signup for the Newsletter!</h3>
</div>
<div class="col-md-3">
<input type="email" title="Email Address for Newsletter" class="form-control email mt-2 mt-md-0" id="mce-EMAIL" placeholder="Your e-mail address" value="" name="EMAIL" required="">
</div>
<div style="position: absolute; left: -5000px;">
<input title="Invisible Field" type="text" name="b_86a6d80146a0da7f2223712e4_73b018498d" tabindex="-1" value="">
</div>
<div class="col-md-auto">
<button type="submit" class="btn btn-theme-background mt-2 mt-md-0 w-100" id="mc-embedded-subscribe"><strong>Subscribe</strong></button>
</div>
</div>
<p class="mb-0 mt-1 text-center"><i>Be the first to know about upcoming features, security releases, and news about Chocolatey.</i></p>
</form>Text Content
1
RESOURCES
Watch videos, read documentation, and hear Chocolatey success stories from
companies you trust.
View Resources
EVENTS
Find past and upcoming webinars, workshops, and conferences. New events have
recently been added!
View Events
COURSES
Step-by-step guides for all things Chocolatey! Earn badges as you learn through
interactive digital courses.
View Courses
--------------------------------------------------------------------------------
Join our monthly Unpacking Software livestream to hear about the latest news,
chat and opinion on packaging, software deployment and lifecycle management!
Learn More
--------------------------------------------------------------------------------
Join the Chocolatey Team on our regular monthly stream where we put a spotlight
on the most recent Chocolatey product releases. You'll have a chance to have
your questions answered in a live Ask Me Anything format.
Learn More
--------------------------------------------------------------------------------
Join us for the Chocolatey Coding Livestream, where members of our team dive
into the heart of open source development by coding live on various Chocolatey
projects. Tune in to witness real-time coding, ask questions, and gain insights
into the world of package management. Don't miss this opportunity to engage with
our team and contribute to the future of Chocolatey!
Learn More
--------------------------------------------------------------------------------
Livestream from
Thursday, 9 June 2022
Join James and Josh to show you how you can get the Chocolatey For Business
recommended infrastructure and workflow, created, in Azure, in around 20
minutes.
Watch On-Demand
--------------------------------------------------------------------------------
Livestreams from
October 2022
For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory,
James, Gary, and Rain as they share knowledge on how to contribute to
open-source projects such as Chocolatey CLI.
Watch On-Demand
--------------------------------------------------------------------------------
Livestream from
Thursday, 04 August 2022
Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the
not so distant future. We'll talk about some cool new features, long term asks
from Customers and Community and how you can get involved!
Watch On-Demand
--------------------------------------------------------------------------------
Join the Chocolatey Team as we discuss all things Community, what we do, how you
can get involved and answer your Chocolatey questions.
Watch The Replays
--------------------------------------------------------------------------------
Webinar from
Wednesday, 17 January 2024
We are delighted to announce the release of Chocolatey Central Management
v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications,
insightful Group Details, an upgraded Dashboard, bug fixes, user interface
polishing, and refined documentation. As an added bonus we'll have members of
our Solutions Engineering team on-hand to dive into some interesting ways you
can leverage the new features available!
Watch On-Demand
--------------------------------------------------------------------------------
Webinar Replay from
Wednesday, 30 March 2022
At Chocolatey Software we strive for simple, and teaching others. Let us teach
you just how simple it could be to keep your 3rd party applications updated
across your devices, all with Intune!
Watch On-Demand
--------------------------------------------------------------------------------
Fill out our survey for a chance to win 🍫 Chocolatey goodies 🍫
* Main
* Community
* Docs
* Blog
* Install
*
1
ctrl k
Search
id:searchValue search by id only
tag:searchValue search by tags
* * Main
* Community
* Docs
* Blog
* Install
*
* Packages
* Learn
* Resources
* Courses
* Product
Products
* Chocolatey for Business
* Pro Edition
* Chocolatey Open Source
* Compare Editions
* Pricing
* Support
Solutions
* Self-Service Anywhere
* Central Management Deployments
* Secure Offline Deployments
Ready to give Chocolatey for Business a Try?
We offer a 14 day white glove free trial to help get you started.
Start Trial
* Connect
* Events
* Careers
* Newsletter
* Chocolatey Community
* Support
* Contact
*
*
*
*
*
*
*
*
*
*
* --------------------------------------------------------------------------------
* Sign In
* Sign Up
* * Profile
* Account
* --------------------------------------------------------------------------------
* Sign Out
* Profile
* Account
* Sign Out
Welcome to the Chocolatey Community Package Repository! The packages found in
this section of the site are provided, maintained, and moderated by the
community.
MODERATION
Every version of each package undergoes a rigorous moderation process before it
goes live that typically includes:
* Security, consistency, and quality checking
* Installation testing
* Virus checking through VirusTotal
* Human moderators who give final review and sign off
More detail at Security and Moderation.
ORGANIZATIONAL USE
If you are an organization using Chocolatey, we want your experience to be fully
reliable. Due to the nature of this publicly offered repository, reliability
cannot be guaranteed. Packages offered here are subject to distribution rights,
which means they may need to reach out further to the internet to the official
locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition
of Chocolatey (including the free open source edition), you can host your own
packages and cache or internalize existing community packages.
DISCLAIMER
Your use of the packages on this site means you understand they are not
supported or guaranteed in any way. Learn more...
I Understand
Generate Script
0 B U I L D E R
* STEP1
Package Review
* STEP2
Integration Method
* STEP3
Install Script / Config
* STEP4
Environment Setup
* STEP5
Install Script
Previous Next
STEP 1: REVIEW YOUR PACKAGES
STEP 2: CHOOSE YOUR INTEGRATION METHOD
* Generic
* Individual
* Ansible
*
* PS DSC
*
STEP 3: ENTER YOUR INTERNAL REPOSITORY URL
(this should look similar to https://community.chocolatey.org/api/v2/)
STEP 3: COPY YOUR SCRIPT OR DOWNLOAD CONFIG
OPTION 1: COPY SCRIPT
OPTION 2: DOWNLOAD CONFIG
Save as .config File
STEP 4: SETUP YOUR ENVIRONMENT
1. ENSURE YOU ARE SET FOR ORGANIZATIONAL DEPLOYMENT
Please see the organizational deployment guide
2. GET THE PACKAGE INTO YOUR ENVIRONMENT
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)
* Open Source or Commercial:
* Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory
Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to
https://community.chocolatey.org/api/v2/. Packages cache on first access
automatically. Make sure your choco clients are using your proxy repository
as a source and NOT the default community repository. See source command
for more information.
* You can also just download the packages and push them to a repository
Download Packages
Option 2: Internalized Package (Reliable, Scalable)
* Open Source
* Download the packages:
Download Packages
* Follow manual internalization instructions
* Package Internalizer (C4B)
* Run: (additional options)
* For package and dependencies run:
* Automate package internalization
STEP 5: COPY YOUR SCRIPT
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places
where you are calling directly to Chocolatey. If you are integrating, keep in
mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes
are shown as failures:
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"
#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
#### We use this variable for future REST calls.
$RequestArguments = @{
UseBasicParsing = $true
}
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "http://internal/odata/repo"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.2.2.nupkg"
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
$TempDirectory = Join-Path $env:Temp "chocolateyInstall"
if (-not (Test-Path $TempDirectory -PathType Container)) {
$null = New-Item -Path $TempDirectory -ItemType Directory
}
$DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments
#### Extract the Nupkg, and run the chocolateyInstall script
if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
} else {
# PowerShell versions <4.0 do not have this function available
try {
$shellApplication = New-Object -ComObject Shell.Application
$zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
$destinationFolder = $shellApplication.NameSpace($TempDirectory)
$destinationFolder.CopyHere($zipPackage.Items(), 0x10)
} catch {
Write-Warning "Unable to unzip package using built-in compression."
throw $_
}
}
& $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
refreshenv
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400
#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress
### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
choco source remove -n $_.Name
}
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco source disable --name chocolatey.licensed
} else {
Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
if ($ChocolateyCentralManagementClientSalt) {
choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
}
if ($ChocolateyCentralManagementServiceSalt) {
choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
}
choco feature enable --name useChocolateyCentralManagement
choco feature enable --name useChocolateyCentralManagementDeployments
}
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy
- name: Install and Configure Chocolatey
hosts: all
## 2. TOP LEVEL VARIABLES ##
vars:
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
nuget_repository_url: http://internal/odata/repo
### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
# nuget_repository_username: username
# nuget_repository_password: password
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService
#### ii. If using a Client Salt, add it here
# chocolatey_central_management_client_salt: clientsalt
#### iii. If using a Service Salt, add it here
# chocolatey_central_management_service_salt: servicesalt
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
tasks:
- name: Install chocolatey
win_chocolatey:
name: chocolatey
source: ""{{ nuget_repository_url }}""
# source_username: ""{{ nuget_repository_username }}""
# source_password: ""{{ nuget_repository_password }}""
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# - name: Enable FIPS compliance
# win_chocolatey_feature:
# name: useFipsCompliantChecksums
# state: enabled
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
- name: Set the cache location
win_chocolatey_config:
name: cacheLocation
state: present
value: C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
- name: Set the command execution timeout
win_chocolatey_config:
name: commandExecutionTimeoutSeconds
state: present
value: 14400
#### Turn off download progress when running choco through integrations
- name: Disable showing download progress
win_chocolatey_feature:
name: showDownloadProgress
state: disabled
### c. Sources ###
#### Remove the default community package repository source
- name: Remove Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey
state: absent
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
- name: Add Internal Repository
win_chocolatey_source:
name: ChocolateyInternal
state: present
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
priority: 1
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
- name: Upgrade Chocolatey
win_chocolatey:
name: chocolatey
state: latest
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
- name: Install Chocolatey License
win_chocolatey:
name: chocolatey-license
source: ChocolateyInternal
state: latest
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
- name: Disable Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey.licensed
state: disabled
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
- name: Install Chocolatey Extension
win_chocolatey:
name: chocolatey.extension
source: ChocolateyInternal
state: latest
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
- name: Hide not-elevated warnings
win_chocolatey_feature:
name: showNonElevatedWarnings
state: disabled
- name: Use background mode for self-service
win_chocolatey_feature:
name: useBackgroundService
state: enabled
- name: Use background service for non-admins
win_chocolatey_feature:
name: useBackgroundServiceWithNonAdministratorsOnly
state: enabled
- name: Allow background uninstallation for user installs
win_chocolatey_feature:
name: allowBackgroundServiceUninstallsFromUserInstallsOnly
state: enabled
- name: Set allowed background service commands
win_chocolatey_config:
name: backgroundServiceAllowedCommands
state: present
value: install,upgrade,uninstall
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
- name: Install Chocolatey Agent
when: chocolatey_central_management_url is defined
win_chocolatey:
name: chocolatey-agent
source: ChocolateyInternal
state: latest
- name: Set the Central Management Service URL
when: chocolatey_central_management_url is defined
win_chocolatey_config:
name: CentralManagementServiceUrl
state: present
value: {{ chocolatey_central_management_url }}
- name: Set the Central Management Client Salt
when: chocolatey_central_management_client_salt is defined
win_chocolatey_config:
name: centralManagementClientCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_client_salt }}
- name: Set the Central Management Service Salt
when: chocolatey_central_management_service_salt is defined
win_chocolatey_config:
name: centralManagementServiceCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_service_salt }}
- name: Use Central Management
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagement
state: enabled
- name: Use Central Management Deployments
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagementDeployments
state: enabled
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "http://internal/odata/repo"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "http://internal/odata/repo/package/chocolatey.2.2.2.nupkg",
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
# action :enable
# end
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
value 'C:\ProgramData\chocolatey\cache'
end
#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
value '14400'
end
#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
action :disable
end
### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
action :remove
end
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
source "#{NugetRepositoryUrl}"
priority 1
action :add
end
execute 'ChocolateyInternal' do
command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
action :upgrade
source "#{NugetRepositoryUrl}"
end
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
action :install
source "#{NugetRepositoryUrl}"
end
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
action :disable
end
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
action install
source "#{NugetRepositoryUrl}"
end
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
action :disable
end
chocolatey_feature 'useBackgroundService' do
action :enable
end
chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
action :enable
end
chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
action :enable
end
chocolatey_config 'backgroundServiceAllowedCommands' do
value 'install,upgrade,uninstall'
end
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
action install
source "#{NugetRepositoryUrl}"
# user "#{NugetRepositoryUsername}"
# password "#{NugetRepositoryPassword}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'CentralManagementServiceUrl' do
value "#{ChocolateyCentralManagementUrl}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementClientSalt}"
only_if { ChocolateyCentralManagementClientSalt != nil }
end
chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementServiceSalt}"
only_if { ChocolateyCentralManagementServiceSalt != nil }
end
chocolatey_feature 'useChocolateyCentralManagement' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_feature 'useChocolateyCentralManagementDeployments' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
$null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
}
Install-Module -Name cChoco
if ($PSGallery.InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
}
}
#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1
Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
param(
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "http://internal/odata/repo",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "http://internal/odata/repo/package/chocolatey.2.2.2.nupkg",
### c. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# ),
### d. Install.ps1 URL
#### The path to the hosted install script:
$ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"
### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt",
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Import-DscResource -ModuleName cChoco
Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
Environment chocoDownloadUrl {
Name = "chocolateyDownloadUrl"
Value = $ChocolateyNupkgUrl
}
cChocoInstaller installChocolatey {
DependsOn = "[Environment]chocoDownloadUrl"
InstallDir = Join-Path $env:ProgramData "chocolatey"
ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# cChocoFeature featureFipsCompliance {
# FeatureName = "useFipsCompliantChecksums"
# }
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
cChocoConfig cacheLocation {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "cacheLocation"
Value = "C:\ProgramData\chocolatey\cache"
}
#### Increase timeout to at least 4 hours
cChocoConfig commandExecutionTimeoutSeconds {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "commandExecutionTimeoutSeconds"
Value = 14400
}
#### Turn off download progress when running choco through integrations
cChocoFeature showDownloadProgress {
DependsOn = "[cChocoInstaller]installChocolatey"
FeatureName = "showDownloadProgress"
Ensure = "Absent"
}
### c. Sources ###
#### Remove the default community package repository source
cChocoSource removeCommunityRepository {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "chocolatey"
Ensure = "Absent"
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
cChocoSource addInternalSource {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "ChocolateyInternal"
Source = $NugetRepositoryUrl
Credentials = $NugetRepositoryCredential
Priority = 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
cChocoPackageInstaller updateChocolatey {
DependsOn = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
Name = "chocolatey"
AutoUpgrade = $true
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
cChocoPackageInstaller chocolateyLicense {
DependsOn = "[cChocoPackageInstaller]updateChocolatey"
Name = "chocolatey-license"
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
Script disableLicensedSource {
DependsOn = "[cChocoPackageInstaller]chocolateyLicense"
GetScript = {
$Source = choco source list --limitoutput | `
ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
Where-Object Name -eq "chocolatey.licensed"
return @{
Result = if ($Source) {
[bool]::Parse($Source.Disabled)
} else {
Write-Warning "Source 'chocolatey.licensed' was not present."
$true # Source does not need disabling
}
}
}
SetScript = {
$null = choco source disable --name "chocolatey.licensed"
}
TestScript = {
$State = [ScriptBlock]::Create($GetScript).Invoke()
return $State.Result
}
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
cChocoPackageInstaller chocolateyLicensedExtension {
DependsOn = "[Script]disableLicensedSource"
Name = "chocolatey.extension"
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
cChocoFeature hideElevatedWarnings {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "showNonElevatedWarnings"
Ensure = "Absent"
}
cChocoFeature useBackgroundService {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundService"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceWithNonAdmins {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
Ensure = "Present"
}
cChocoConfig allowedBackgroundServiceCommands {
DependsOn = "[cChocoFeature]useBackgroundService"
ConfigName = "backgroundServiceAllowedCommands"
Value = "install,upgrade,uninstall"
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
cChocoPackageInstaller chocolateyAgent {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
Name = "chocolatey-agent"
}
cChocoConfig centralManagementServiceUrl {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "CentralManagementServiceUrl"
Value = $ChocolateyCentralManagementUrl
}
if ($ChocolateyCentralManagementClientSalt) {
cChocoConfig centralManagementClientSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementClientSalt
}
}
if ($ChocolateyCentralManagementServiceSalt) {
cChocoConfig centralManagementServiceSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementServiceSalt
}
}
cChocoFeature useCentralManagement {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagement"
Ensure = "Present"
}
cChocoFeature useCentralManagementDeployments {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagementDeployments"
Ensure = "Present"
}
}
}
}
# If working this into an existing configuration with a good method for
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
}
)
}
try {
Push-Location $env:Temp
$Config = ChocolateyConfig -ConfigurationData $ConfigData
Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
Pop-Location
}
Copy
Requires Puppet Chocolatey Provider module. See docs at
https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
#### See https://forge.puppet.com/puppetlabs/chocolatey
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'http://internal/odata/repo'
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'http://internal/odata/repo/package/chocolatey.2.2.2.nupkg'
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'
#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
### source locations. This is directly to the bare download url for the
### chocolatey.nupkg, similar to what you see when you browse to
### https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
chocolatey_download_url => $_choco_download_url,
use_7zip => false,
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#chocolateyfeature {'useFipsCompliantChecksums':
# ensure => enabled,
#}
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
value => 'C:\ProgramData\chocolatey\cache',
}
#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
value => '14400',
}
#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
ensure => disabled,
}
### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
ensure => absent,
location => 'https://community.chocolatey.org/api/v2/',
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
ensure => present,
location => $_repository_url,
priority => 1,
username => 'optional',
password => 'optional,not ensured',
bypass_proxy => true,
admin_only => false,
allow_self_service => false,
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
package {'chocolatey':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license
# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
ensure => disabled,
priority => '10',
user => 'customer',
password => '1234',
require => Package['chocolatey-license'],
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
ensure => disabled,
}
chocolateyfeature {'useBackgroundService':
ensure => enabled,
}
chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
ensure => enabled,
}
chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
ensure => enabled,
}
chocolateyconfig {'backgroundServiceAllowedCommands':
value => 'install,upgrade,uninstall',
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
package {'chocolatey-agent':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
chocolateyconfig {'CentralManagementServiceUrl':
value => $_chocolatey_central_management_url,
}
if $_chocolatey_central_management_client_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
if $_chocolatey_central_management_service_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
chocolateyfeature {'useChocolateyCentralManagement':
ensure => enabled,
require => Package['chocolatey-agent'],
}
chocolateyfeature {'useChocolateyCentralManagementDeployments':
ensure => enabled,
require => Package['chocolatey-agent'],
}
}
Copy
Previous Next
Need Help? View our docs or file an issue.
THERE IS ALREADY A VERSION OF THIS PACKAGE IN YOUR SCRIPT BUILDER
Current Version New Version
Delete and Add New Version Cancel
Downloads:
1,854,948
Downloads of v 3.1.4:
34,204
Last Update:
02 NOV 2023
Package Maintainer(s):
* Iristyle
* chocolatey-community
Software Author(s):
* Shining Light Productions
Tags:
openssl-light openssl ssl tls pfx pem key rsa admin foss cross-platform
* Software Specific:
* Software Site
* Software License
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
OPENSSL – THE OPEN SOURCE SSL AND TLS TOOLKIT
* 1
* 2
* 3
3.1.4 | Updated: 02 Nov 2023
Show Additional Links
* Software Specific:
* Software Site
* Software License
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
Downloads:
1,854,948
Downloads of v 3.1.4:
34,204
Maintainer(s):
* Iristyle
* chocolatey-community
Software Author(s):
* Shining Light Productions
Tags:
openssl-light openssl ssl tls pfx pem key rsa admin foss cross-platform
OPENSSL – THE OPEN SOURCE SSL AND TLS TOOLKIT 3.1.4
* 1
* 2
* 3
SOME CHECKS HAVE FAILED OR ARE NOT YET COMPLETE
Not All Tests Have Passed
Hide Checks
Hide Checks
--------------------------------------------------------------------------------
Validation Testing Passed
--------------------------------------------------------------------------------
Verification Testing Passed
Details
--------------------------------------------------------------------------------
Scan Testing Resulted in Flagged as a Note:
At least one file within this package has greater than 0 detections, but less
than 5
Details
*
*
* Generic
* Individual
* Ansible
*
* PS DSC
*
Add to Script Builder Learn More
--------------------------------------------------------------------------------
DEPLOYMENT METHOD: INDIVIDUAL INSTALL, UPGRADE, & UNINSTALL
* Install
* Upgrade
* Uninstall
To install OpenSSL – The Open Source SSL and TLS toolkit, run the following
command from the command line or from PowerShell:
>
To upgrade OpenSSL – The Open Source SSL and TLS toolkit, run the following
command from the command line or from PowerShell:
>
To uninstall OpenSSL – The Open Source SSL and TLS toolkit, run the following
command from the command line or from PowerShell:
>
DEPLOYMENT METHOD:
NOTE
This applies to both open source and commercial editions of Chocolatey.
1. ENTER YOUR INTERNAL REPOSITORY URL
(this should look similar to https://community.chocolatey.org/api/v2/)
--------------------------------------------------------------------------------
2. SETUP YOUR ENVIRONMENT
1. ENSURE YOU ARE SET FOR ORGANIZATIONAL DEPLOYMENT
Please see the organizational deployment guide
2. GET THE PACKAGE INTO YOUR ENVIRONMENT
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)
* Open Source or Commercial:
* Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory
Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to
https://community.chocolatey.org/api/v2/. Packages cache on first access
automatically. Make sure your choco clients are using your proxy repository
as a source and NOT the default community repository. See source command
for more information.
* You can also just download the package and push it to a repository Download
Option 2: Internalized Package (Reliable, Scalable)
* Open Source
* Download the package:
Download
* Follow manual internalization instructions
* Package Internalizer (C4B)
* Run: (additional options)
choco download openssl.light --internalize --source=https://community.chocolatey.org/api/v2/
Copy
* For package and dependencies run:
You must enter your internal repository url above before proceeding.
choco push --source="'http://internal/odata/repo'"
Copy
* Automate package internalization
--------------------------------------------------------------------------------
3. COPY YOUR SCRIPT
You must enter your internal repository url above before proceeding.
choco upgrade openssl.light -y --source="'http://internal/odata/repo'" [other options]
Copy
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places
where you are calling directly to Chocolatey. If you are integrating, keep in
mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes
are shown as failures:
You must enter your internal repository url above before proceeding.
choco upgrade openssl.light -y --source="'http://internal/odata/repo'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
Copy
You must enter your internal repository url above before proceeding.
- name: Install openssl.light
win_chocolatey:
name: openssl.light
version: '3.1.4'
source: http://internal/odata/repo
state: present
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
You must enter your internal repository url above before proceeding.
chocolatey_package 'openssl.light' do
action :install
source 'http://internal/odata/repo'
version '3.1.4'
end
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
You must enter your internal repository url above before proceeding.
cChocoPackageInstaller openssl.light
{
Name = "openssl.light"
Version = "3.1.4"
Source = "http://internal/odata/repo"
}
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
You must enter your internal repository url above before proceeding.
package { 'openssl.light':
ensure => '3.1.4',
provider => 'chocolatey',
source => 'http://internal/odata/repo',
}
Copy
Requires Puppet Chocolatey Provider module. See docs at
https://forge.puppet.com/puppetlabs/chocolatey.
--------------------------------------------------------------------------------
4. IF APPLICABLE - CHOCOLATEY CONFIGURATION/INSTALLATION
See infrastructure management matrix for Chocolatey configuration elements and
examples.
Package Approved
This package was approved as a trusted package on 02 Nov 2023.
Description
--------------------------------------------------------------------------------
The OpenSSL Project is a collaborative effort to develop a robust,
commercial-grade, full-featured, and Open Source toolkit implementing the Secure
Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as
well as a full-strength general purpose cryptography library. The project is
managed by a worldwide community of volunteers that use the Internet to
communicate, plan, and develop the OpenSSL toolkit and its related
documentation.
The Win32 OpenSSL Installation Project is dedicated to providing a simple
installation of OpenSSL. It is easy to set up and easy to use through the
simple, effective installer. No need to compile anything or jump through any
hoops, just click a few times and it is installed, leaving you to doing real
work. Download it today! Note that these are default builds of OpenSSL and
subject to local and state laws. More information can be found in the legal
agreement of the installation.
PACKAGE PARAMETERS
* /InstallDir:- Installation directory, defaults to the 'Program Files\OpenSSL'
directory.
Example: choco install openssl.light --params "/InstallDir:C:\your\install\path"
Files
--------------------------------------------------------------------------------
Show legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The embedded software have been downloaded from the listed download
location on <https://slproweb.com/products/Win32OpenSSL.html>
and can be verified by doing the following:
1. Download the following:
32-Bit software: <https://slproweb.com/download/Win32OpenSSL_Light-3_1_4.exe>
64-Bit software: <https://slproweb.com/download/Win64OpenSSL_Light-3_1_4.exe>
2. Get the checksum using one of the following methods:
- Using powershell function 'Get-FileHash'
- Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:
checksum type: sha256
checksum32: A6FEE205765B88D35C1895F62A786B89CFB64166F0C1C29E22E752E18C4E4068
checksum64: 4224DD7AC1347A5DB88DAFDE63B58A48E8369CF339C6E3AB346CA2840C4DDB6E
The file 'LICENSE.txt' has been obtained from <https://www.openssl.org/source/license.txt>
Show legal\LICENSE.txt
LICENSE ISSUES
==============
The OpenSSL toolkit stays under a double license, i.e. both the conditions of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts.
OpenSSL License
---------------
/* ====================================================================
* Copyright (c) 1998-2017 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* openssl-core@openssl.org.
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software written by Eric Young
* (eay@cryptsoft.com). This product includes software written by Tim
* Hudson (tjh@cryptsoft.com).
*
*/
Original SSLeay License
-----------------------
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young (eay@cryptsoft.com).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young (eay@cryptsoft.com)"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
*/
Show tools\Win64OpenSSL_Light-3_1_4.exe
md5: B0FAEA1B478D8FF9D38446219A1559AB | sha1: 70C80097838D8E1C1C9580360647704BE2B521F1 | sha256: 4224DD7AC1347A5DB88DAFDE63B58A48E8369CF339C6E3AB346CA2840C4DDB6E | sha512: AE7E02502F7AB34CA2C20293FD06B2156A428D9D8B73DA8908DC1EC148988AA80BC63DB7472D86C23BF3F992EF1FA8F58C20618961867B326A3FF2E0039A5BAB
Show tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
$pp = Get-PackageParameters
$silentArgs = '/silent','/sp-','/suppressmsgboxes'
$silentArgs += '/DIR="{0}"' -f $( if ($pp.InstallDir) { $pp.InstallDir } else { "$Env:ProgramFiles\OpenSSL" } )
$packageArgs = @{
packageName = 'OpenSSL.Light'
fileType = 'exe'
file = "$toolsPath\Win32OpenSSL_Light-3_1_4.exe"
file64 = "$toolsPath\Win64OpenSSL_Light-3_1_4.exe"
softwareName = 'OpenSSL*Light*'
silentArgs = $silentArgs
validExitCodes = @(0)
}
Install-ChocolateyInstallPackage @packageArgs
Remove-Item -Force -ea 0 "$toolsPath\*.exe","$toolsPath\*.ignore"
$installLocation = Get-AppInstallLocation $packageArgs.softwareName
if (!$installLocation) { Write-Warning "Can't find install location, PATH not updated"; return }
Write-Host "Installed to '$installLocation'"
Install-ChocolateyPath -PathToInstall "$installLocation\bin" -PathType Machine
Show tools\Win32OpenSSL_Light-3_1_4.exe
md5: 8D80EA186526EC90C721C2CDB9CECB6F | sha1: 8EE92F461B5D1B33FD57A3E7657B0B9BB2681EB1 | sha256: A6FEE205765B88D35C1895F62A786B89CFB64166F0C1C29E22E752E18C4E4068 | sha512: 32959646F1B27360E1566DF15E8854E87F8148AEB3BFAC4D9FC800211336B2A56A1902D60EF49E031268AC888E975BC0E4755B9E3443DBCD406B3EB659B3B1A1
Virus Scan Results
--------------------------------------------------------------------------------
Log in or click on link to see number of positives.
* OpenSSL.Light.3.1.4.nupkg (979dad62bfb4) - ## / 64
* Win32OpenSSL_Light-3_1_4.exe (a6fee205765b) - ## / 72
* Win64OpenSSL_Light-3_1_4.exe (4224dd7ac134) - ## / 72
In cases where actual malware is found, the packages are subject to removal.
Software sometimes has false positives. Moderators do not necessarily validate
the safety of the underlying software, only that a package retrieves software
from the official distribution point and/or validate embedded software against
official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version History
Add to Builder Version Downloads Last Updated Status OpenSSL – The Open Source
SSL and TLS toolkit 3.1.4 34204 Thursday, November 2, 2023 Approved OpenSSL –
The Open Source SSL and TLS toolkit 3.1.3 8862 Thursday, September 28, 2023
Approved OpenSSL – The Open Source SSL and TLS toolkit 3.1.2 10459 Wednesday,
August 2, 2023 Approved OpenSSL – The Open Source SSL and TLS toolkit 3.1.1
13296 Wednesday, May 31, 2023 Approved OpenSSL – The Open Source SSL and TLS
toolkit 3.1.0 16202 Wednesday, March 15, 2023 Approved OpenSSL – The Open Source
SSL and TLS toolkit 3.0.8 7431 Thursday, February 9, 2023 Approved OpenSSL – The
Open Source SSL and TLS toolkit 3.0.7 223699 Wednesday, November 2, 2022
Approved OpenSSL – The Open Source SSL and TLS toolkit 3.0.5 122663 Wednesday,
July 6, 2022 Approved OpenSSL – The Open Source SSL and TLS toolkit 3.0.4 6773
Wednesday, June 22, 2022 Approved OpenSSL – The Open Source SSL and TLS toolkit
3.0.3 88166 Wednesday, May 4, 2022 Approved OpenSSL – The Open Source SSL and
TLS toolkit 3.0.2 49512 Wednesday, March 16, 2022 Approved OpenSSL – The Open
Source SSL and TLS toolkit 3.0.1 55576 Wednesday, December 15, 2021 Approved
OpenSSL – The Open Source SSL and TLS toolkit 3.0.0 92968 Thursday, September 9,
2021 Approved OpenSSL – The Open Source SSL and TLS toolkit 1.1.1.20181020
833133 Saturday, October 20, 2018 Approved OpenSSL – The Open Source SSL and TLS
toolkit 1.1.1 40847 Friday, September 14, 2018 Approved OpenSSL – The Open
Source SSL and TLS toolkit 1.1.0.80000000 29836 Tuesday, August 14, 2018
Approved OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.70000000 80811
Tuesday, March 27, 2018 Approved OpenSSL – The Open Source SSL and TLS toolkit
1.1.0.60000000 41268 Saturday, November 4, 2017 Approved OpenSSL – The Open
Source SSL and TLS toolkit 1.1.0.50000001 20306 Wednesday, June 28, 2017
Approved OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.50000000 6165
Friday, May 26, 2017 Approved OpenSSL – The Open Source SSL and TLS toolkit
1.1.0.40000001 3198 Saturday, May 6, 2017 Approved OpenSSL – The Open Source SSL
and TLS toolkit 1.1.0.40000000 1602 Thursday, April 27, 2017 Approved OpenSSL –
The Open Source SSL and TLS toolkit 1.1.0.20170216 14173 Thursday, February 16,
2017 Approved OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.20170126 3498
Thursday, January 26, 2017 Approved OpenSSL – The Open Source SSL and TLS
toolkit 1.1.0.20161111 8972 Friday, November 11, 2016 Approved OpenSSL – The
Open Source SSL and TLS toolkit 1.1.0.20160926 6136 Monday, September 26, 2016
Approved OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.20160923 694
Friday, September 23, 2016 Approved OpenSSL – The Open Source SSL and TLS
toolkit 1.1.0 3125 Saturday, August 27, 2016 Approved OpenSSL – The Open Source
SSL and TLS toolkit 1.0.2.20160710 3535 Sunday, July 10, 2016 Approved OpenSSL –
The Open Source SSL and TLS toolkit 1.0.2.20160504 513 Wednesday, May 4, 2016
Approved OpenSSL – The Open Source SSL and TLS toolkit 1.0.2.20160428 792
Thursday, April 28, 2016 Approved OpenSSL – The Open Source SSL and TLS toolkit
1.0.2.20160302 3218 Wednesday, March 2, 2016 Approved OpenSSL – The Open Source
SSL and TLS toolkit 1.0.2.20160130 1826 Saturday, January 30, 2016 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.0.2.20151205 3253 Saturday,
December 5, 2015 Approved OpenSSL – The Open Source SSL and TLS toolkit
1.0.2.20151010 3704 Saturday, October 10, 2015 Approved OpenSSL – The Open
Source SSL and TLS toolkit 1.0.2.20150710 3283 Friday, July 10, 2015 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.0.2.20150704 598 Saturday, July
4, 2015 Approved OpenSSL – The Open Source SSL and TLS toolkit 1.0.2.20150627
606 Saturday, June 27, 2015 Approved OpenSSL – The Open Source SSL and TLS
toolkit 1.0.2.20150613 843 Saturday, June 13, 2015 Approved OpenSSL – The Open
Source SSL and TLS toolkit 1.0.2.20150612 478 Friday, June 12, 2015 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.0.2.20150320 1619 Friday, March
20, 2015 Approved OpenSSL – The Open Source SSL and TLS toolkit 1.0.2 994
Monday, March 2, 2015 Approved OpenSSL – The Open Source SSL and TLS toolkit
1.0.1.20150209 711 Monday, February 9, 2015 Approved OpenSSL - The Open Source
SSL and TLS toolkit 1.0.1.20141015 1013 Thursday, November 13, 2014 Approved
OpenSSL - The Open Source SSL and TLS toolkit 1.0.1.20140824 946 Sunday, August
24, 2014 Approved OpenSSL - The Open Source SSL and TLS toolkit 1.0.1.20140411
860 Friday, April 11, 2014 Approved OpenSSL - The Open Source SSL and TLS
toolkit 1.0.1.20130603 1004 Monday, June 3, 2013 Approved OpenSSL - The Open
Source SSL and TLS toolkit 1.0.1.20121127 650 Wednesday, November 28, 2012
Approved OpenSSL - The Open Source SSL and TLS toolkit 1.0.1.3 927 Friday,
October 12, 2012 Approved
Show Additional Versions
Copyright
--------------------------------------------------------------------------------
Ⓒ 2000-2003 Shining Light Productions
Dependencies
--------------------------------------------------------------------------------
* * chocolatey (≥ 0.10.5)
* chocolatey-core.extension (≥ 1.3.3)
* vcredist140 (≥ 14.12.25810)
Discussion for the OpenSSL – The Open Source SSL and TLS toolkit Package
--------------------------------------------------------------------------------
GROUND RULES:
* This discussion is only about OpenSSL – The Open Source SSL and TLS toolkit
and the OpenSSL – The Open Source SSL and TLS toolkit package. If you have
feedback for Chocolatey, please contact the Google Group.
* This discussion will carry over multiple versions. If you have a comment
about a particular version, please note that in your comments.
* The maintainers of this Chocolatey Package will be notified about new
comments that are posted to this Disqus thread, however, it is NOT a
guarantee that you will get a response. If you do not hear back from the
maintainers after posting a message below, please follow up by using the link
on the left side of this page or follow this link to contact maintainers. If
you still hear nothing back, please follow the package triage process.
* Tell us what you love about the package or OpenSSL – The Open Source SSL and
TLS toolkit, or tell us what needs improvement.
* Share your experiences with the package, or extra configuration or gotchas
that you've found.
* If you use a url, the comment will be flagged for moderation until you've
been whitelisted. Disqus moderated comments are approved on a weekly schedule
if not sooner. It could take between 1-5 days for your comment to show up.
SIGNUP FOR THE NEWSLETTER!
Subscribe
Be the first to know about upcoming features, security releases, and news about
Chocolatey.
OVERVIEW
* Getting Started Guide
* Security
* Privacy Policy
* Partner
* Terms of Use
PRODUCT
* C4B Trial
* Pricing
* Support
* Community Packages
LEARN
* Docs
* Courses
* Sitemap
* Blog
CONNECT
* Contact Us
* Support
* Newsletter
* Shop
* Report a Bug
* Status
* *
*
*
*
*
*
*
*
*
*
© 2024 Chocolatey Software, Inc.
Deployed from fd3f30d63a. You are on EC2AMAZ-M3H3MB7. Page generated 13 Mar 2024
08:18:39 +00:00.
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept
Please enable JavaScript to view the comments powered by Disqus.