Go to file
Pauli 96d6a4e446 test: add a comment indication that a bad MAC is intentional
This permits negative testing of FIPS module load failure.

Also changed the MAC to all zeros to make it even clearer.

Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/16168)
2021-07-28 10:35:06 +10:00
.github ci: disable async for the SH4 build and reenable the associated test 2021-07-28 10:30:45 +10:00
apps apps: Use the first detected address family if IPv6 is not available 2021-07-16 08:58:06 +02:00
Configurations Makefile: Avoid changing LIBDIR based on whether it already exists 2021-07-23 09:08:28 +02:00
crypto Don't try and load the config file while already loading the config file 2021-07-28 10:35:06 +10:00
demos demos: update readme file with pbkdf2 and scrypt examples. 2021-07-20 10:14:42 +10:00
dev Ensure ordinals are created during release process 2021-06-29 09:51:30 +10:00
doc Mark the EVP_PKEY_METHOD arg as const on some EVP_PKEY_meth_get_*() funcs 2021-07-27 10:34:44 +01:00
engines afalg: add some memory initialisation calls to pacify memory sanitisation. 2021-07-01 13:18:58 +10:00
external/perl
fuzz Update copyright year 2021-06-17 13:24:59 +01:00
gost-engine@62583fb222 Updated gost-engine to latest commit from master branch 2021-05-07 15:43:26 +02:00
include Don't try and load the config file while already loading the config file 2021-07-28 10:35:06 +10:00
krb5@aa9b4a2a64 Update dependencies for krb5 external test 2021-06-23 10:26:53 +02:00
ms Update copyright year 2021-04-22 14:38:44 +01:00
os-dep
providers Don't leak the OSSL_LIB_CTX in the event of a failure to load the FIPS module 2021-07-28 10:34:53 +10:00
pyca-cryptography@0034926f2c update pyca-cryptography regression test suite 2021-07-02 13:05:29 +10:00
ssl KTLS: AES-CCM in TLS-1.3 is broken on 5.x kernels, disable it 2021-07-27 13:19:20 +10:00
test test: add a comment indication that a bad MAC is intentional 2021-07-28 10:35:06 +10:00
tools Move some OpenSSL perl utility functions to OpenSSL::Util 2021-05-19 10:13:02 +02:00
util EVP: Add EVP_PKEY_get0_provider() and EVP_PKEY_CTX_get0_provider() 2021-07-26 12:11:54 +02:00
VMS VMS documentation fixes 2021-02-12 15:57:25 +01:00
wycheproof@2196000605 add wycheproof submodule 2021-04-27 19:09:03 +10:00
.gitattributes Remove the external BoringSSL test 2021-03-26 14:24:06 +01:00
.gitignore Add wrap.pl to .gitignore 2021-06-26 11:39:10 +10:00
.gitmodules add wycheproof submodule 2021-04-27 19:09:03 +10:00
ACKNOWLEDGEMENTS.md
appveyor.yml Simplify AppVeyor configuration 2021-05-01 13:13:11 +10:00
AUTHORS.md Add some missing committers to the AUTHORS list 2021-02-02 16:45:44 +01:00
build.info Building: Add necessary dependencies for linker scripts and .rc files 2021-06-11 17:22:44 +02:00
CHANGES.md tls_process_{client,server}_certificate(): allow verify_callback return > 1 2021-07-21 11:46:18 +02:00
config
config.com Update copyright year 2020-07-16 14:47:04 +02:00
configdata.pm.in configdata.pm: Allow extra arguments when --query is given. 2021-05-29 11:02:37 +02:00
Configure config: enable ACVP test case if FIPS is enabled. 2021-07-17 17:51:08 +10:00
CONTRIBUTING.md Drop Travis 2021-01-25 13:41:23 +01:00
e_os.h Remove I_CAN_LIVE_WITH_LNK4049 2021-06-09 18:01:22 +10:00
FAQ.md
HACKING.md Fix many MarkDown issues in {NOTES*,README*,HACKING,LICENSE}.md files 2020-07-05 11:29:43 +02:00
INSTALL.md Enable ssl-trace by default 2021-06-10 09:42:12 +01:00
LICENSE.txt
NEWS.md Prepare for 3.0 beta 2 2021-06-17 14:03:53 +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 cross-compile considerations for NonStop x86 builds. 2021-07-01 11:46:08 +10:00
NOTES-PERL.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
NOTES-UNIX.md Unify the markdown links to the NOTES and README files 2021-02-12 20:41:32 +01:00
NOTES-VALGRIND.md Unify the markdown links to the NOTES and README files 2021-02-12 20:41:32 +01:00
NOTES-VMS.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
NOTES-WINDOWS.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
README-ENGINES.md README-ENGINES: fix the link to the provider API README 2021-02-15 19:33:53 +01:00
README-FIPS.md Add migration guide for 3.0 2021-05-20 08:44:08 +01:00
README-PROVIDERS.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
README.md Unify the markdown links to the NOTES and README files 2021-02-12 20:41:32 +01:00
SUPPORT.md Fix SUPPORT.md for better readability 2020-11-14 16:42:41 +01:00
VERSION.dat Prepare for 3.0 beta 2 2021-06-17 14:03:53 +01:00

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, 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-2021 The OpenSSL Project

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

All rights reserved.