A local copy of OpenSSL from GitHub
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Pauli 88ce406c89 ssl: coverity 1465527 - dereference after null check 9 months ago
.github ci: add a no-legacy build 9 months ago
Configurations Fix the perl code to get FIPSMODULENAME 9 months ago
VMS VMS documentation fixes 10 months ago
apps apps: fix Coverity 1472670 & 1472685: resource leaks 9 months ago
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 5 years ago
crypto async: coverity 1446224 - dereference after null check 9 months ago
demos Update the demos/README file because it is really old. New demos should provide best practice for API use. 9 months ago
dev Update copyright year 10 months ago
doc Added functions for printing EVP_PKEYs to FILE * 9 months ago
engines Update copyright year 9 months ago
external/perl Update the bundled external perl module Text-Template to version 1.56 2 years ago
fuzz Update copyright year 9 months ago
gost-engine@28a0a19354 CI: add job with external tests 9 months ago
include Make ossl_d2i_PUBKEY_legacy() completely libcrypto internal 9 months ago
krb5@890ca2f401 Update the krb5 submodule 2 years ago
ms Unify all assembler file generators 2 years ago
os-dep Move Haiku configuration to separate config file to denote 6 years ago
providers rsa: fix coverity 1472658: resource leak 9 months ago
pyca-cryptography@e09cd90f77 CI: add job with external tests 9 months ago
ssl ssl: coverity 1465527 - dereference after null check 9 months ago
test test: coverity 1455749 - dereference after null check 9 months ago
tools Update copyright year 9 months ago
util Added functions for printing EVP_PKEYs to FILE * 9 months ago
.gitattributes TEST: Make our test data binary 1 year ago
.gitignore Fix some missed usage of DEFINE_LHASH_OF() 1 year ago
.gitmodules GOST external tests 2 years ago
.travis-apt-pin.preferences Fix travis clang-3.9 builds 5 years ago
.travis-create-release.sh Remove all 'make dist' artifacts 3 years ago
ACKNOWLEDGEMENTS.md Fix issues reported by markdownlint 2 years ago
AUTHORS.md Add some missing committers to the AUTHORS list 10 months ago
CHANGES.md TS and CMS CAdES-BES: Refactor check_signing_certs() funcs into common ESS func 9 months ago
CONTRIBUTING.md Drop Travis 10 months ago
Configure Configure: check all DEPEND values against GENERATE, not just .h files 9 months ago
FAQ.md doc: introduce some minimalistic markdown without essential changes 2 years ago
HACKING.md Fix many MarkDown issues in {NOTES*,README*,HACKING,LICENSE}.md files 1 year ago
INSTALL.md Fix error-checking compiles for mutex 9 months ago
LICENSE.txt Rename NOTES*, README*, VERSION, HACKING, LICENSE to .md or .txt 1 year ago
NEWS.md Prepare for 3.0 alpha 14 9 months ago
NOTES-ANDROID.md Unify the markdown links to the NOTES and README files 10 months ago
NOTES-DJGPP.md Unify the markdown links to the NOTES and README files 10 months ago
NOTES-NONSTOP.md Rewrite the HPE NonStop Notes file in Markdown with more explanations. 1 year ago
NOTES-PERL.md Reformat some NOTES and README files 10 months ago
NOTES-UNIX.md Unify the markdown links to the NOTES and README files 10 months ago
NOTES-VALGRIND.md Unify the markdown links to the NOTES and README files 10 months ago
NOTES-VMS.md Reformat some NOTES and README files 10 months ago
NOTES-WINDOWS.md NOTES-WINDOWS: fix typo 10 months ago
README-ENGINES.md README-ENGINES: fix the link to the provider API README 10 months ago
README-FIPS.md Update README-FIPS.md 9 months ago
README-PROVIDERS.md Add a skeleton README-PROVIDERS file 10 months ago
README.md Unify the markdown links to the NOTES and README files 10 months ago
SUPPORT.md Fix SUPPORT.md for better readability 1 year ago
VERSION.dat Prepare for 3.0 alpha 14 9 months ago
appveyor.yml appveyor.yml: clarify conditions for building the plain configuration 9 months ago
build.info Configuration: ensure that 'no-tests' works correctly 10 months ago
config config: Turn into a simple wrapper 1 year ago
config.com Update copyright year 1 year ago
configdata.pm.in configdata.pm.in, util/dofile.pl: Make a HERE document stricter. 1 year ago
e_os.h Implement OpenSSL secure memory for Windows 1 year ago


Welcome to the OpenSSL Project

openssl logo

github actions ci badge appveyor badge

OpenSSL is a robust, commercial-grade, full-featured Open Source Toolkit for the Transport Layer Security (TLS) protocol formerly known as the Secure Sockets Layer (SSL) protocol. The protocol implementation is based on a full-strength general purpose cryptographic library, which can also be used stand-alone.

OpenSSL is descended from the SSLeay library developed by Eric A. Young and Tim J. Hudson.

The official Home Page of the OpenSSL Project is www.openssl.org.

Table of Contents


The OpenSSL toolkit includes:

  • libssl an implementation of all TLS protocol versions up to TLSv1.3 (RFC 8446).

  • libcrypto a full-strength general purpose cryptographic library. It constitutes the basis of the TLS implementation, but can also be used independently.

  • openssl the OpenSSL command line tool, a swiss army knife for cryptographic tasks, testing and analyzing. It can be used for

    • creation of key parameters
    • creation of X.509 certificates, CSRs and CRLs
    • calculation of message digests
    • encryption and decryption
    • SSL/TLS client and server tests
    • handling of S/MIME signed or encrypted mail
    • and more...


For Production Use

Source code tarballs of the official releases can be downloaded from www.openssl.org/source. The OpenSSL project does not distribute the toolkit in binary form.

However, for a large variety of operating systems precompiled versions of the OpenSSL toolkit are available. In particular on Linux and other Unix operating systems it is normally recommended to link against the precompiled shared libraries provided by the distributor or vendor.

For Testing and Development

Although testing and development could in theory also be done using the source tarballs, having a local copy of the git repository with the entire project history gives you much more insight into the code base.

The official OpenSSL Git Repository is located at git.openssl.org. There is a GitHub mirror of the repository at github.com/openssl/openssl, which is updated automatically from the former on every commit.

A local copy of the Git Repository can be obtained by cloning it from the original OpenSSL repository using

git clone git://git.openssl.org/openssl.git

or from the GitHub mirror using

git clone https://github.com/openssl/openssl.git

If you intend to contribute to OpenSSL, either to fix bugs or contribute new features, you need to fork the OpenSSL repository openssl/openssl on GitHub and clone your public fork instead.

git clone https://github.com/yourname/openssl.git

This is necessary, because all development of OpenSSL nowadays is done via GitHub pull requests. For more details, see Contributing.

Build and Install

After obtaining the Source, have a look at the INSTALL file for detailed instructions about building and installing OpenSSL. For some platforms, the installation instructions are amended by a platform specific document.

Specific notes on upgrading to OpenSSL 3.0 from previous versions, as well as known issues are available on the OpenSSL 3.0 Wiki page.


Manual Pages

The manual pages for the master branch and all current stable releases are available online.


There is a Wiki at wiki.openssl.org which is currently not very active. It contains a lot of useful information, not all of which is up to date.


OpenSSL is licensed under the Apache License 2.0, which means that you are free to get and use it for commercial and non-commercial purposes as long as you fulfill its conditions.

See the LICENSE.txt file for more details.


There are various ways to get in touch. The correct channel depends on your requirement. see the SUPPORT file for more details.


If you are interested and willing to contribute to the OpenSSL project, please take a look at the CONTRIBUTING file.


A number of nations restrict the use or export of cryptography. If you are potentially subject to such restrictions you should seek legal advice before attempting to develop or distribute cryptographic code.


Copyright (c) 1998-2021 The OpenSSL Project

Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson

All rights reserved.