Downloads:

510,470

Downloads of v 1.0.1.20121127:

518

Last Update:

28 Nov 2012

Package Maintainer(s):

Software Author(s):

  • Shining Light Productions

Tags:

openssl SSL TLS pfx pem key RSA

OpenSSL - The Open Source SSL and TLS toolkit

This is not the latest version of OpenSSL - The Open Source SSL and TLS toolkit available.

1.0.1.20121127 | Updated: 28 Nov 2012

Downloads:

510,470

Downloads of v 1.0.1.20121127:

518

Maintainer(s):

Software Author(s):

  • Shining Light Productions

Tags:

openssl SSL TLS pfx pem key RSA

OpenSSL - The Open Source SSL and TLS toolkit 1.0.1.20121127

This is not the latest version of OpenSSL - The Open Source SSL and TLS toolkit available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

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:

>

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 openssl.light -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 openssl.light -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 openssl.light installed
  win_chocolatey:
    name: openssl.light
    state: present
    version: 1.0.1.20121127
    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 'openssl.light' do
  action    :install
  version  '1.0.1.20121127'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: openssl.light,
    Version: 1.0.1.20121127,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller openssl.light
{
   Name     = 'openssl.light'
   Ensure   = 'Present'
   Version  = '1.0.1.20121127'
   Source   = 'STEP 3 URL'
}

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


package { 'openssl.light':
  provider => 'chocolatey',
  ensure   => '1.0.1.20121127',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install openssl.light version="1.0.1.20121127" 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 02 Mar 2015.

Description

This is really 1.0.1c, but the Nuget spec doesn't allow such version identifiers, so the file versions are used.

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.

Log in or click on link to see number of positives.

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
OpenSSL – The Open Source SSL and TLS toolkit 1.1.1.20181020 229477 Saturday, October 20, 2018 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.1 38417 Friday, September 14, 2018 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.80000000 29383 Tuesday, August 14, 2018 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.70000000 80153 Tuesday, March 27, 2018 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.60000000 38802 Saturday, November 4, 2017 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.50000001 20142 Wednesday, June 28, 2017 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.50000000 5817 Friday, May 26, 2017 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.40000001 3016 Saturday, May 6, 2017 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.40000000 1431 Thursday, April 27, 2017 Approved
OpenSSL – The Open Source SSL and TLS toolkit 1.1.0.20170216 14039 Thursday, February 16, 2017 Approved

Changes between 1.0.1b and 1.0.1c [10 May 2012]

*) Sanity check record length before skipping explicit IV in TLS
1.2, 1.1 and DTLS to avoid DoS attack.

Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
fuzzing as a service testing platform.
(CVE-2012-2333)
[Steve Henson]

*) Initialise tkeylen properly when encrypting CMS messages.
Thanks to Solar Designer of Openwall for reporting this issue.
[Steve Henson]

*) In FIPS mode don't try to use composite ciphers as they are not
approved.
[Steve Henson]

Changes between 1.0.1a and 1.0.1b [26 Apr 2012]

*) OpenSSL 1.0.0 sets SSL_OP_ALL to 0x80000FFFL and OpenSSL 1.0.1 and
1.0.1a set SSL_OP_NO_TLSv1_1 to 0x00000400L which would unfortunately
mean any application compiled against OpenSSL 1.0.0 headers setting
SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disablng
TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to
0x10000000L Any application which was previously compiled against
OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1
will need to be recompiled as a result. Letting be results in
inability to disable specifically TLS 1.1 and in client context,
in unlike event, limit maximum offered version to TLS 1.0 [see below].
[Steve Henson]

*) In order to ensure interoperabilty SSL_OP_NO_protocolX does not
disable just protocol X, but all protocols above X if there are
protocols below X still enabled. In more practical terms it means
that if application wants to disable TLS1.0 in favor of TLS1.1 and
above, it's not sufficient to pass SSL_OP_NO_TLSv1, one has to pass
SSL_OP_NO_TLSv1|SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2. This applies to
client side.
[Andy Polyakov]

Changes between 1.0.1 and 1.0.1a [19 Apr 2012]

*) Check for potentially exploitable overflows in asn1_d2i_read_bio
BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
in CRYPTO_realloc_clean.

Thanks to Tavis Ormandy, Google Security Team, for discovering this
issue and to Adam Langley <[email protected]> for fixing it.
(CVE-2012-2110)
[Adam Langley (Google), Tavis Ormandy, Google Security Team]

*) Don't allow TLS 1.2 SHA-256 ciphersuites in TLS 1.0, 1.1 connections.
[Adam Langley]

*) Workarounds for some broken servers that "hang" if a client hello
record length exceeds 255 bytes:

1. Do not use record version number > TLS 1.0 in initial client
hello: some (but not all) hanging servers will now work.
2. If we set OPENSSL_MAX_TLS1_2_CIPHER_LENGTH this will truncate
the number of ciphers sent in the client hello. This should be
set to an even number, such as 50, for example by passing:
-DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 to config or Configure.
Most broken servers should now work.
3. If all else fails setting OPENSSL_NO_TLS1_2_CLIENT will disable
TLS 1.2 client support entirely.
[Steve Henson]

*) Fix SEGV in Vector Permutation AES module observed in OpenSSH.
[Andy Polyakov]

This package has no dependencies.

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.
comments powered by Disqus