Go to file
Rohan McLure 2f1112b22a Fix unrolled montgomery multiplication for POWER9
In the reference C implementation in bn_asm.c, tp[num + 1] contains the
carry bit for accumulations into tp[num]. tp[num + 1] is only ever
assigned, never itself incremented.

Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/18883)
2022-08-17 13:00:50 +02:00
.github Implement AES-GCM-SIV (RFC8452) 2022-07-29 08:32:16 -04:00
apps APPS: genrsa: Support setting properties 2022-08-17 09:20:41 +02:00
Configurations Fix quotes install_fips in Configurations/windows-makefile.tmpl 2022-07-28 10:08:51 +01:00
crypto Fix unrolled montgomery multiplication for POWER9 2022-08-17 13:00:50 +02:00
demos
dev
doc Correct the documentation for OPENSSL_MALLOC_FD 2022-08-17 12:57:48 +02:00
engines
external/perl
fuzz
gost-engine@b2b4d629f1
include Make OSSL_TIME a structure 2022-08-12 15:44:01 +01:00
krb5@aa9b4a2a64
ms
oqs-provider@e422884c23
os-dep
providers providers: Set the size of EC signature on s390. 2022-08-04 09:14:20 -04:00
pyca-cryptography@fa84d185c0
python-ecdsa@4de8d5bf89
ssl Make OSSL_TIME a structure 2022-08-12 15:44:01 +01:00
test APPS: genrsa: Support setting properties 2022-08-17 09:20:41 +02:00
tlsfuzzer@dbd56c1490
tlslite-ng@771e9f59d6
tools
util Give BIO_s_mem() the ability to support datagrams 2022-07-28 08:06:52 +01:00
VMS
wycheproof@2196000605
.gitattributes
.gitignore
.gitmodules
ACKNOWLEDGEMENTS.md
appveyor.yml
AUTHORS.md
build.info
CHANGES.md Add some documentation for the BIO_s_mem() datagram capability 2022-07-28 08:06:53 +01:00
config
config.com
configdata.pm.in
Configure Don't try to make configuration leaner 2022-07-24 04:08:46 +02:00
CONTRIBUTING.md
FAQ.md
HACKING.md
INSTALL.md Remove no-{ssl|tls|tls1_3|dtls}-method in INSTALL.md 2022-07-27 13:26:47 +02:00
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.