Go to file
Matt Caswell 55ff8fb4ed Design for the Fault Injector
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Hugo Landau <hlandau@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/19877)
2023-01-31 11:34:15 +11:00
.github Revert "CI: cross-compile: riscv: Add RV64 machine with Zb* and Zk*" 2023-01-26 10:20:14 +01:00
apps APPS: generated certs bear X.509 V3, unless -x509v1 option of req app is given 2023-01-24 15:16:47 +01:00
Configurations Adding a separated build settings for BSD flavors 2023-01-20 11:04:50 +00:00
crypto Do not include sparse_array.o in libssl with no-shared 2023-01-31 11:10:22 +11:00
demos
dev
doc Design for the Fault Injector 2023-01-31 11:34:15 +11:00
engines Padlock: fix byte swapping assembly for AES-192 and 256 2023-01-20 07:31:33 +00:00
external/perl
fuzz
gost-engine@a6b90523e4 APPS: generated certs bear X.509 V3, unless -x509v1 option of req app is given 2023-01-24 15:16:47 +01:00
include QUIC Probes Support: Minor tweaks 2023-01-30 09:44:59 +01:00
krb5@aa9b4a2a64
ms
oqs-provider@3f3d8a8cf3
os-dep
providers ChaCha20-Poly1305 no longer supports truncated IV's. 2023-01-30 09:48:50 +01:00
pyca-cryptography@7e33b0e773
python-ecdsa@4de8d5bf89
ssl QUIC Probes Support: Minor tweaks 2023-01-30 09:44:59 +01:00
test Workaround crash in atexit on NonStop platforms 2023-01-31 11:04:24 +11:00
tlsfuzzer@dbd56c1490
tlslite-ng@771e9f59d6
tools
util Implement BIO_s_dgram_mem() reusing the BIO_s_dgram_pair() code 2023-01-27 16:11:38 +01:00
VMS
wycheproof@2196000605
.gitattributes
.gitignore
.gitmodules
ACKNOWLEDGEMENTS.md
appveyor.yml
AUTHORS.md
build.info
CHANGES.md [doc] Sync documentation now that 3.0 honors OSSL_PKEY_PARAM_EC_POINT_CONVERSION_FORMAT 2023-01-31 11:08:31 +11:00
CODE-OF-CONDUCT.md
config
config.com
configdata.pm.in
Configure
CONTRIBUTING.md
FAQ.md
HACKING.md
INSTALL.md
LICENSE.txt
NEWS.md
NOTES-ANDROID.md
NOTES-DJGPP.md
NOTES-NONSTOP.md
NOTES-PERL.md
NOTES-UNIX.md
NOTES-VALGRIND.md
NOTES-VMS.md
NOTES-WINDOWS.md
README-ENGINES.md
README-FIPS.md
README-PROVIDERS.md
README.md
SUPPORT.md
VERSION.dat

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

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 can be found in the migration_guide(7ossl) manual 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-2022 The OpenSSL Project

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

All rights reserved.