Go to file
Matt Caswell 533390e46f Ensure calling BIO_recvmmsg() with a dgram pair reports errors
When calling BIO-recvmmsg() and using a dgram pair we were failing to
raise an error in the case that a problem occurs. This means that the
reason behind a failure cannot be detected and all problems are treated
as fatal even if they may not be.

Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20030)
2023-02-22 05:34:05 +00:00
.github ci: Add djgpp build 2023-02-08 09:20:02 -05:00
apps OSSL_CMP_certConf_cb(): fix regression on checking newly enrolled cert 2023-02-13 11:56:10 +01:00
Configurations
crypto Ensure calling BIO_recvmmsg() with a dgram pair reports errors 2023-02-22 05:34:05 +00:00
demos
dev Fix treatment of BUILD_METADATA 2022-12-08 07:01:33 +01:00
doc update documentation to note that EdDSA is not FIPS approved 2023-02-22 11:29:02 +11:00
engines Padlock: fix byte swapping assembly for AES-192 and 256 2023-01-20 07:31:33 +00:00
external/perl
fuzz obj: Add SM4 XTS OID 2022-11-29 16:17:30 +01:00
gost-engine@a6b90523e4
include Don't treat the Tserver as connected until the handshake is confirmed 2023-02-22 05:34:04 +00:00
krb5@aa9b4a2a64
ms
oqs-provider@3f3d8a8cf3
os-dep
providers Revert "Put EdDSA back as approved algorithms." 2023-02-22 11:29:02 +11:00
pyca-cryptography@7e33b0e773
python-ecdsa@4de8d5bf89
ssl Don't treat the Tserver as connected until the handshake is confirmed 2023-02-22 05:34:04 +00:00
test Add a helper function to prepend a frame to a packet 2023-02-22 05:34:05 +00:00
tlsfuzzer@dbd56c1490
tlslite-ng@771e9f59d6
tools
util
VMS
wycheproof@2196000605
.gitattributes Remove the external BoringSSL test 2021-03-26 14:24:06 +01:00
.gitignore Update gitignore 2022-08-19 13:11:36 -04:00
.gitmodules Add external testing with oqsprovider 2022-03-09 17:57:37 +01:00
ACKNOWLEDGEMENTS.md Fix various typos, repeated words, align some spelling to LDP. 2022-10-12 16:55:28 +11:00
appveyor.yml Simplify AppVeyor configuration 2021-05-01 13:13:11 +10:00
AUTHORS.md
build.info
CHANGES.md update changes entry to note EdDSA is not FIPS approved 2023-02-22 11:29:02 +11:00
CODE-OF-CONDUCT.md Add CODE-OF-CONDUCT.md 2022-08-18 16:32:23 +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:04 +01:00
Configure
CONTRIBUTING.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
FAQ.md doc: introduce some minimalistic markdown without essential changes 2020-02-26 21:04:38 +01:00
HACKING.md
INSTALL.md
LICENSE.txt Rename NOTES*, README*, VERSION, HACKING, LICENSE to .md or .txt 2020-07-05 11:29:43 +02:00
NEWS.md Correct a copy&paste error in a link URL 2023-02-11 15:01:20 +01:00
NOTES-ANDROID.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
NOTES-DJGPP.md
NOTES-NONSTOP.md Document limits on static and dynamic linking for HPE NonStop platforms. 2023-02-08 16:09:58 +01:00
NOTES-PERL.md Fix various typos, repeated words, align some spelling to LDP. 2022-10-12 16:55:28 +11:00
NOTES-UNIX.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
NOTES-VALGRIND.md
NOTES-VMS.md Fix issues found by md-nits 2021-05-28 11:14:46 +02:00
NOTES-WINDOWS.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
README-ENGINES.md
README-FIPS.md Update FIPS related build instructions. 2022-12-16 19:08:49 +01:00
README-PROVIDERS.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
README.md Fixed some grammar and spelling 2022-10-09 17:40:29 +02:00
SUPPORT.md Fix Markdown links in SUPPORT.md 2021-12-08 15:09:36 +11:00
VERSION.dat Change all references to OpenSSL 3.1 to OpenSSL 3.2 in the master branch 2022-10-07 10:05:50 +02: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 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.