Downloads:

1,013

Downloads of v 2.5.5:

639

Last Update:

7/25/2017

Package Maintainer(s):

Software Author(s):

  • OpenBSD Foundation

Tags:

libressl admin

libressl (Install)

2.5.5 | Updated: 7/25/2017

Downloads:

1,013

Downloads of v 2.5.5:

639

Maintainer(s):

Software Author(s):

  • OpenBSD Foundation

Tags:

libressl admin

libressl (Install) 2.5.5

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install libressl (Install), run the following command from the command line or from PowerShell:

>

To upgrade libressl (Install), run the following command from the command line or from PowerShell:

>

To uninstall libressl (Install), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade libressl -y --source="'STEP 3 URL'" [other options]

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:


choco upgrade libressl -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure libressl installed
  win_chocolatey:
    name: libressl
    state: present
    version: 2.5.5
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'libressl' do
  action    :install
  version  '2.5.5'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: libressl,
    Version: 2.5.5,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller libressl
{
   Name     = 'libressl'
   Ensure   = 'Present'
   Version  = '2.5.5'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'libressl':
  provider => 'chocolatey',
  ensure   => '2.5.5',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install libressl version="2.5.5" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 9/4/2019.

Description

SSL Tools from the OpenBSD Project

 The binaries that are extracted from the ZIP will always match the
 platform (64-bit binaries on 64-bit OS, 32-bit binaries on 32-bit OS).

 PARAMETERS

    If neither none of the install folder parameters is  used, this install will 
    perform a a regular Chocolatey "portable install"" where the exes in the package 
    are placed in a special chocolatey folder and shim EXEs are created in 
    Chocolatey's bin folder, making them immediately available on the path.

    -params '"/ProgramFilesInstall"'
    [OPTIONAL]
    LibreSSL will be installed to "$env:programfiles\LibreSSL" and this location
    will be added to the system path.
    If you use this option a clean uninstall will be possible (uninstall routines
    check for it as a standard, alternative location).

    -params '"/ProgramDataInstall"'
    [OPTIONAL]
    LibreSSL will be installed to "$env:programdata\LibreSSL" and this location
    will be added to the system path.
    If you use this option a clean uninstall will be possible (uninstall routines
    check for it as a standard, alternative location).

    -params '"/InstallDir:c:\yourcustomdir\LibreSSL"'
    -params '"/InstallDir:c:\yourcustomdir"'
    LibreSSL will be installed to your custom location and this location
    will be added to the system path.
    If you use this option a clean uninstall will NOT be possible because
    the custom install location is not remembered by the package.

tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; 

$version = '2.5.5'
$packageName   = 'libressl'
$toolsDir      = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$FileFullPath = Join-Path $toolsDir 'libressl-2.5.5-windows.zip'

$OSBits = Get-ProcessorBits
If ($OSBits -eq 64)
{$SpecificFolder = "libressl-$version-windows\x64"}
Else
{$SpecificFolder = "libressl-$version-windows\x86"}


$packageArgs = @{
  packageName   = $packageName
  FileFullPath = $FileFullPath
  Destination = $toolsDir
  SpecificFolder = $SpecificFolder
  softwareName  = 'libressl*'
}

$checksum      = 'C825AE3DF24ABFC04545C0A5269884D3FAEEB1BB'
$checksumType  = 'sha1'


Write-Host "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

$minchocoversion = '0.10.4.0'
If (($env:CHOCOLATEY_VERSION) -AND ([version]$env:CHOCOLATEY_VERSION -lt [version]$minchocoversion))
{
  # -SpecificFolder functionality of Install-ChocolateyUnzip is broken before 10.4 (https://github.com/chocolatey/choco/pull/1023)
  Throw "You must have Chocolatey `"$minchocoversion`" or later to run this package."
}

If ([bool](get-command Get-ChecksumValid -ea silentlycontinue))
{
  If (![bool](Get-ChecksumValid -File $FileFullPath -checksumType $checksumType -checksum $checksum))
  {
    Write-Output "Hashes for internal source match"
  }
  Else
  {
    throw "Checksums for internal source do not match - something is wrong."
  }
}
Else
{
  Write-Output "Source files are internal to the package, checksums are not required nor checked."
}


# Now parse the packageParameters using good old regular expression
$arguments = @{};
$packageParameters = $env:chocolateyPackageParameters
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    #"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
          $arguments.Add(
              $_.Groups[$option_name].Value.Trim(),
              $_.Groups[$value_name].Value.Trim())
      }
    }
    else
    {
      throw "Package Parameters were found but were invalid (REGEX Failure)"
    }

    if ($arguments.ContainsKey("ProgramFilesInstall")) {

      $InstallDir = "$env:programfiles\LibreSSL"
      Write-Host "/ProgramFilesInstall was used, installing to `"$InstallDir`" and adding `"$InstallDir`" to the System path."
      Write-Host "Clean uninstall will be possible."

    }    

    if ($arguments.ContainsKey("ProgramDataInstall")) {

      $InstallDir = "$env:programdata\LibreSSL"
      Write-Host "/ProgramFilesInstall was used, installing to `"$InstallDir`" and adding `"$InstallDir`" to the System path."
      Write-Host "Clean uninstall will be possible."

    }    

    if ($arguments.ContainsKey("InstallDir")) {

      $InstallDir = $arguments.Get_Item("InstallDir")
      Write-Host "/InstallDir was used, installing to `"$InstallDir`" and adding `"$InstallDir`" to the System path."
      Write-Host "Clean Uninstall will not be possible - after uninstall, remove `"$InstallDir`" from the file system and machine path."

    }

} else {
    Write-Debug "No Package Parameters Passed in";
}

Get-ChocolateyUnZip @packageArgs

If (!$InstallDir)
{
  Move-Item "$toolsdir\$specificfolder\*" "$toolsdir" -force
}
Else
{

  Function Ensure-OnPath ($PathToAdd,$Scope,$PathVariable,$AddToStartOrEnd)
  {
    If (!$Scope) {$Scope='Machine'}
    If (!$PathVariable) {$PathVariable='PATH'}
    If (!$AddToStartOrEnd) {$AddToStartOrEnd='END'}
    If (($PathToAdd -ilike '*%*') -AND ($Scope -ieq 'Process')) {Throw 'Unexpanded environment variables do not work on the Process level path'}
    write-host "Ensuring `"$pathtoadd`" is added to the $AddToStartOrEnd of variable `"$PathVariable`" for scope `"$scope`" "
    $ExistingPathArray = @([Environment]::GetEnvironmentVariable("$PathVariable","$Scope").split(';'))
    if (($ExistingPathArray -inotcontains $PathToAdd) -AND ($ExistingPathArray -inotcontains "$PathToAdd\"))
    {
      If ($AddToStartOrEnd -ieq 'START')
      { $Newpath = @("$PathToAdd") + $ExistingPathArray }
      else 
      { $Newpath = $ExistingPathArray + @("$PathToAdd")  }
      $AssembledNewPath = ($newpath -join(';')).trimend(';')
      [Environment]::SetEnvironmentVariable("$PathVariable",$AssembledNewPath,"$Scope")
    }
  }

  If (!(Test-Path "$InstallDir"))
  {New-Item "$InstallDir" -ItemType Directory | out-null }
  
  Move-Item "$toolsdir\$specificfolder\*" "$InstallDir" -force

  Ensure-OnPath "$InstallDir" 'Machine'  
  Write-output "`"$InstallDir`" was added to Machine path - use refreshenv to make the path available in the same process where the package was installed."

}
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'; 

$packageName   = 'libressl'
$toolsDir      = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

If (Test-Path "$env:ProgramFiles\LibreSSL")
{
$DefaultInstallDir = "$env:ProgramFiles\LibreSSL"
}

If (Test-Path "$env:ProgramData\LibreSSL")
{
$DefaultInstallDir = "$env:ProgramData\LibreSSL"
}

If (("$DefaultInstallDir") -AND (Test-Path "$DefaultInstallDir"))
{
  Write-Host "Found $packagename in default program files folder `"$DefaultInstallDir`", uninstalling..."
  Remove-Item "$DefaultInstallDir" -recurse -force

  Function Ensure-RemovedFromPath ($PathToRemove,$Scope,$PathVariable)
  {
    If (!$Scope) {$Scope='Machine'}
    If (!$PathVariable) {$PathVariable='PATH'}
    $ExistingPathArray = @([Environment]::GetEnvironmentVariable("$PathVariable","$Scope").split(';'))
    write-host "Ensuring `"$PathToRemove`" is removed from variable `"$PathVariable`" for scope `"$scope`" "
    if (($ExistingPathArray -icontains $PathToRemove) -OR ($ExistingPathArray -icontains "$PathToRemove\"))
    {
      foreach ($path in $ExistingPathArray)
      {
        If ($Path)
        {
          If (($path -ine "$PathToRemove") -AND ($path -ine "$PathToRemove\"))
          {
            [string[]]$Newpath += "$path"
          }
        }
      }
      $AssembledNewPath = ($Newpath -join(';')).trimend(';')
      [Environment]::SetEnvironmentVariable("$PathVariable",$AssembledNewPath,"$Scope")
    }
  }

  Ensure-RemovedFromPath "$DefaultInstallDir" 'Machine'
}
tools\libressl-2.5.5-windows.zip
md5: 6229AADB39FF5CAA892707F57FC2CF1E | sha1: C825AE3DF24ABFC04545C0A5269884D3FAEEB1BB | sha256: 21EDEBA00EAB78A5AF8302BF5543BADE4DA53D584EDC4E56D67DBB91EDF2A56C | sha512: 5C416FD994855765AB021155406049B17D9C414C38EA44B3AFE3A4D01A6B26C88F09B1591D0017FFBEE679D8A39711C6A27CB633BDEEC41D25FAA56E8A72691F
tools\LICENSE.txt

  LICENSE ISSUES
  ==============

  The OpenSSL toolkit stays under a dual 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. Actually both licenses are BSD-style
  Open Source licenses. In case of any license issues related to OpenSSL
  please contact [email protected]

  OpenSSL License
  ---------------

/* ====================================================================
 * Copyright (c) 1998-2011 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
 *    [email protected]
 *
 * 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
 * ([email protected]).  This product includes software written by Tim
 * Hudson ([email protected]).
 *
 */

 Original SSLeay License
 -----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young ([email protected]).
 * 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 ([email protected]).
 * 
 * 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 ([email protected])"
 *    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 ([email protected])"
 * 
 * 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.]
 */
tools\VERIFICATION.txt

VERIFICATION
The package internally verifies it's checksum.

The SHA256 checksum for the enclosed zip is found here: https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/SHA256


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 Downloads Last Updated Status
libressl (Install) 2.5.3 374 Sunday, May 21, 2017 Approved

This package has no dependencies.

Discussion for the libressl (Install) Package

Ground Rules:

  • This discussion is only about libressl (Install) and the libressl (Install) 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 libressl (Install), 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.
comments powered by Disqus