TLS/SSL and crypto library
Go to file
Matt Caswell c3cc0f1386 Prepare for release of 3.0.12
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Release: yes
2023-10-24 14:48:41 +01:00
.github Windows CI: Add some non-default options to check they are working 2023-10-13 15:09:27 +02:00
Configurations Update unix Makefile template to handle paths with spaces 2023-10-18 09:24:27 +02:00
VMS Fix VMS installation - Check the presence of providers in the IVP script 2021-12-14 11:48:39 +00:00
apps Copyright year updates 2023-10-24 14:47:21 +01:00
crypto Copyright year updates 2023-10-24 14:47:21 +01:00
demos Add Demos for DSA params/DSA keygen. 2022-12-22 12:10:12 +01:00
dev Fix treatment of BUILD_METADATA 2022-12-08 07:23:27 +01:00
doc Copyright year updates 2023-10-24 14:47:21 +01:00
engines Copyright year updates 2023-08-01 14:46:02 +01:00
external/perl
fuzz Copyright year updates 2023-09-19 14:58:35 +02:00
gost-engine@2a8a5e0eca New version of gost-engine tests 2023-08-04 09:51:01 -04:00
include Copyright year updates 2023-10-24 14:47:21 +01:00
krb5@aa9b4a2a64 Update dependencies for krb5 external test 2021-06-23 10:26:53 +02:00
ms
os-dep Fix copyrights 2022-02-03 13:58:55 +01:00
providers make update 2023-10-24 14:48:41 +01:00
pyca-cryptography@c18d056738 Update pyca-cryptography submodule to 38.0.4 2022-12-22 10:13:19 +01:00
ssl Copyright year updates 2023-09-19 14:58:35 +02:00
test Copyright year updates 2023-10-24 14:47:21 +01:00
tools c_rehash: Drop the issuer_name_hash= prefix from the CRL hash 2022-06-20 11:45:57 +01:00
util Add documentation for the function SSL_CONF_CTX_finish. 2023-09-20 10:26:36 +10:00
wycheproof@2196000605
.gitattributes Remove the external BoringSSL test 2021-03-26 14:24:06 +01:00
.gitignore Update .gitignore 2022-05-06 15:40:46 +02:00
.gitmodules add wycheproof submodule 2021-04-27 19:09:03 +10:00
ACKNOWLEDGEMENTS.md always use the same perl in $PATH 2021-09-02 12:56:29 +10:00
AUTHORS.md Add some missing committers to the AUTHORS list 2021-02-02 16:45:44 +01:00
CHANGES.md Prepare for release of 3.0.12 2023-10-24 14:48:41 +01:00
CONTRIBUTING.md Fix broken link to coding-style.html 2022-04-04 08:27:16 +10:00
Configure no-module should not imply disabling DSO loading support 2023-07-17 09:41:31 +10:00
FAQ.md doc: introduce some minimalistic markdown without essential changes 2020-02-26 21:04:38 +01:00
HACKING.md Fix many MarkDown issues in {NOTES*,README*,HACKING,LICENSE}.md files 2020-07-05 11:29:43 +02:00
INSTALL.md Fix parenthesis, use a colon 2023-10-13 17:24:35 +02:00
LICENSE.txt
NEWS.md Prepare for release of 3.0.12 2023-10-24 14:48:41 +01:00
NOTES-ANDROID.md Unify the markdown links to the NOTES and README files 2021-02-12 20:41:32 +01:00
NOTES-DJGPP.md Unify the markdown links to the NOTES and README files 2021-02-12 20:41:32 +01:00
NOTES-NONSTOP.md Document limits on static and dynamic linking for HPE NonStop platforms. 2023-02-08 16:09:48 +01:00
NOTES-PERL.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
NOTES-UNIX.md Add a clarification to NOTES-UNIX.md 2021-08-23 15:19:31 +02:00
NOTES-VALGRIND.md changes opensssl typos to openssl 2021-12-10 15:19:04 +11:00
NOTES-VMS.md Add information on the 'ias' port for OpenVMS 2023-05-22 08:31:19 +02:00
NOTES-WINDOWS.md Fix formatting of NOTES-WINDOWS.md and doc-nits failure 2022-03-25 10:04:25 +01:00
README-ENGINES.md Fix trivial check_docs CI failure 2022-10-21 17:59:23 +02:00
README-FIPS.md Add FIPS build instructions 2023-07-14 11:36:05 +10:00
README-PROVIDERS.md docs: correct manual page links for version 3.0 2022-03-11 17:23:31 +01:00
README.md Copyright year updates 2023-09-19 14:58:35 +02:00
SUPPORT.md Fix Markdown links in SUPPORT.md 2021-12-08 15:10:23 +11:00
VERSION.dat Prepare for release of 3.0.12 2023-10-24 14:48:41 +01:00
build.info Remove include/openssl/configuration.h from mandatory dependencies 2022-05-25 22:43:29 +02:00
config config: Turn into a simple wrapper 2020-06-28 18:34:36 +02:00
config.com Update copyright year 2020-07-16 14:47:04 +02:00
configdata.pm.in Use $config{build_file} instead of $target{build_file} 2023-02-01 08:30:38 +01:00
e_os.h djgpp: Use usleep() for ossl_sleep() 2022-09-29 12:04:00 +02:00

README.md

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-2023 The OpenSSL Project

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

All rights reserved.