Cryptography and SSL/TLS Toolkit


The master sources are maintained in our git repository, which is accessible over the network and cloned on GitHub, at Bugs and pull patches (issues and pull requests) should be filed on the GitHub repo. Please familiarize yourself with the license.

The table below lists the latest releases for every branch. (For an explanation of the numbering, see our release strategy.) All releases can be found at /source/old. A list of mirror sites can be found here.

KBytes  Date   File 
17184  2023-Sep-28 13:41:30  openssl-3.2.0-alpha2.tar.gz (SHA256) (PGP sign) (SHA1)
14842  2023-Sep-19 13:29:45  openssl-3.0.11.tar.gz (SHA256) (PGP sign) (SHA1)
15197  2023-Sep-19 13:29:45  openssl-3.1.3.tar.gz (SHA256) (PGP sign) (SHA1)
9661  2023-Sep-11 14:46:17  openssl-1.1.1w.tar.gz (SHA256) (PGP sign) (SHA1)

Note: The latest stable version is the 3.1 series supported until 14th March 2025. Also available is the 3.0 series which is a Long Term Support (LTS) version and is supported until 7th September 2026. The previous LTS version (the 1.1.1 series) is also available but has recently gone out of support. Users should transition to 3.0 or 3.1 as soon as possible. A pre-release (not for production use) version of our forthcoming 3.2 release is also available for testing purposes. All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used. Users of these older versions are encouraged to upgrade to 3.1 or 3.0 as soon as possible. Extended support for 1.1.1 and 1.0.2 to gain access to security fixes for that version is available.

The following OpenSSL version(s) are FIPS validated:

 OpenSSL Version   Certificate   Security Policy 
3.0.8 certificate security policy
3.0.0 certificate security policy

For a list of CVEs and their impact on validated FIPS providers, visit the CVEs and FIPS page.

Please follow the Security Policy instructions to download, build and install a validated OpenSSL FIPS provider. Other OpenSSL Releases MAY use the validated FIPS provider, but MUST NOT build and use their own FIPS provider. For example you can build OpenSSL 3.1 and use the OpenSSL 3.0.8 FIPS provider with it.

Information about how to configure and use the FIPS provider in your applications is available on the FIPS module man page. You must also read the module security policy and follow the specific build and installation instructions included in it.

For an overview of some of the key concepts in OpenSSL 3.1 and 3.0 see the libcrypto manual page. Information and notes about migrating existing applications to OpenSSL 3.1 (and 3.0) are available in the OpenSSL 3.1 Migration Guide

When building a release for the first time, please make sure to look at the INSTALL file in the distribution along with any NOTES file applicable to your platform. If you have problems, look at the FAQ, which can be found online. If you still need more help, then join the openssl-users email list and post a question there.

PGP keys for the signatures are available from the OTC page. Current members that sign releases include Richard Levitte, Matt Caswell, Paul Dale, and Tomas Mraz.

The releases can be also signed by the OpenSSL OMC key with fingerprint EFC0 A467 D613 CB83 C7ED 6D30 D894 E2CE 8B3D 79F5.

Each day we make a snapshot of each development branch. They can be found at These daily snapshots of the source tree are provided for convenience only and not even guaranteed to compile. Note that keeping a git local repository and updating it every 24 hours is equivalent and will often be faster and more efficient.


Please remember that export/import and/or use of strong cryptography software, providing cryptography hooks, or even just communicating technical details about cryptography software is illegal in some parts of the world. So when you import this package to your country, re-distribute it from there or even just email technical suggestions or even source patches to the authors or other people you are strongly advised to pay close attention to any laws or regulations which apply to you. The authors of OpenSSL are not liable for any violations you make here. So be careful, it is your responsibility.