Go to file
Agustin Gianni 48116c2d0f Fix incorrect use of BN_CTX API
In some edge cases BN_CTX_end was being called without first calling
BN_CTX_start. This creates a situation where the state of the big
number allocator is corrupted and may lead to crashes.

Fixes #13812

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/13813)
2021-01-13 10:35:27 +01:00
.github GitHub CI: Separate no-deprecated job from minimal job 2020-12-19 17:02:12 +01:00
apps Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
boringssl@2070f8ad91
Configurations Mac M1 setting change proposal. 2021-01-06 11:06:32 +01:00
crypto Fix incorrect use of BN_CTX API 2021-01-13 10:35:27 +01:00
demos
dev dev/release.sh: improve instruction for pushing the tag 2020-10-17 11:54:34 +02:00
doc Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
engines Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
external/perl
fuzz Fix 'no-deprecated' 2020-12-19 17:02:12 +01:00
gost-engine@b008f2a0ff Update gost-engine to fix API rename 2020-08-07 23:13:14 +03:00
include Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
krb5@890ca2f401
ms
os-dep
providers Fix enable-weak-ssl-ciphers 2021-01-13 09:04:49 +00:00
pyca-cryptography@09403100de
ssl Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
test x509_vfy.c: Fix a regression in find_issuer() 2021-01-13 09:09:36 +01:00
tools
util Add X509_NAME_hash_ex() to be able to check if it failed due to unsupported SHA1 2021-01-13 09:09:36 +01:00
VMS
.gitattributes TEST: Make our test data binary 2020-11-24 11:01:58 +01:00
.gitignore Fix some missed usage of DEFINE_LHASH_OF() 2020-10-30 14:24:30 +00:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml {.travis,ci,appveyor}.yml: Make minimal config consistent, add no-deprecated no-ec no-ktls no-siv 2020-12-04 16:20:53 +01:00
ACKNOWLEDGEMENTS.md
appveyor.yml {.travis,ci,appveyor}.yml: Make minimal config consistent, add no-deprecated no-ec no-ktls no-siv 2020-12-04 16:20:53 +01:00
AUTHORS.md
build.info Remove duplicate GENERATE declarations for .pod files 2021-01-12 11:25:55 +01:00
CHANGES.md Add SM2 private key range validation 2021-01-08 23:59:02 +02:00
config
config.com
configdata.pm.in configdata.pm.in, util/dofile.pl: Make a HERE document stricter. 2020-10-27 10:17:19 +01:00
Configure Configure: warn about duplicate GENERATE declarations in build.info files 2021-01-12 11:25:54 +01:00
CONTRIBUTING.md Change markdown link style in README, INSTALL, SUPPORT and CONTRIBUTING 2020-10-18 13:28:08 +02:00
e_os.h Implement OpenSSL secure memory for Windows 2020-10-22 12:11:35 +10:00
FAQ.md
HACKING.md
INSTALL.md {.travis,ci,appveyor}.yml: Make minimal config consistent, add no-deprecated no-ec no-ktls no-siv 2020-12-04 16:20:53 +01:00
LICENSE.txt
NEWS.md Prepare for 3.0 alpha 11 2021-01-07 13:48:32 +00:00
NOTES-Android.md
NOTES-DJGPP.md
NOTES-NONSTOP.md Rewrite the HPE NonStop Notes file in Markdown with more explanations. 2020-10-28 17:18:26 +01:00
NOTES-Perl.md
NOTES-Unix.md
NOTES-Valgrind.md
NOTES-VMS.md
NOTES-Windows.txt Fix markdown nits in NOTES-Windows.txt 2020-09-10 08:57:55 +10:00
README-Engine.md
README-FIPS.md
README.md README: Move Travis link to .com from .org. 2020-11-28 15:38:12 +10:00
SUPPORT.md Fix SUPPORT.md for better readability 2020-11-14 16:42:41 +01:00
VERSION.dat Prepare for 3.0 alpha 11 2021-01-07 13:48:32 +00:00

Welcome to the OpenSSL Project

openssl logo

travis 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

Overview

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...

Download

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.

Documentation

Manual Pages

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

Wiki

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.

License

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.

Support

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

Contributing

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

Legalities

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

Copyright (c) 1998-2020 The OpenSSL Project

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

All rights reserved.