Go to file
Benjamin Kaduk fa4d3fe46d Fix krb5 external test
Since commit c3845ceba8 ("Build file
templates: don't set OPENSSL_{ENGINES,MODULES}") the krb5 external test
has been failing.  This is because it relied on OPENSSL_MODULES already
being set -- even though it did assign to OPENSSL_MODULES itself (and
thus got skipped by the cleanup pass in that commit), it was doing so
only to canonicalize the existing value to an absolute path, not as a de
novo assignment.

Catch up to the rest of the tree and just set it directly as the
"providers" path from the build top (but still canonicalized to an
absolute path).

[extended tests]

Fixes: 11492

Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/11499)
2020-04-09 15:33:52 -07:00
.github
apps Move legacy ciphers into the legacy provider 2020-04-09 12:47:46 +10:00
boringssl@2070f8ad91
Configurations EVP & TLS: Add necessary EC_KEY data extraction functions, and use them 2020-04-08 15:30:25 +02:00
crypto Add common internal crypto/ modules in liblegacy.a 2020-04-09 19:49:06 +02:00
demos
doc Document the new library context aware CT functions 2020-04-09 14:51:48 +01:00
engines
external/perl
fuzz
include Enable Ed25519 signing/verifying to use the libctx 2020-04-09 16:10:00 +01:00
krb5@890ca2f401
ms
os-dep
providers Enable Ed25519 signing/verifying to use the libctx 2020-04-09 16:10:00 +01:00
pyca-cryptography@09403100de
ssl Ensure libssl uses the new library context aware CT code 2020-04-09 14:51:48 +01:00
test Fix krb5 external test 2020-04-09 15:33:52 -07:00
tools
util Make the CT code library context aware 2020-04-09 14:51:48 +01:00
VMS
.gitattributes
.gitignore Add the auto generated der files to .gitignore 2020-04-09 15:02:30 +01:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml Travis build matrix adjustments 2020-04-09 09:20:37 +02:00
ACKNOWLEDGEMENTS.md
appveyor.yml
AUTHORS.md
build.info
CHANGES.md Fixups in CHANGES.md 2020-04-01 21:25:10 +02:00
config
config.com
configdata.pm.in
Configure
CONTRIBUTING.md
e_os.h
FAQ.md
HACKING
INSTALL.md
LICENSE
NEWS.md NEWS: note OSSL_PARAM_BLD API as public. 2020-03-28 12:27:22 +10:00
NOTES.ANDROID
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX
NOTES.VALGRIND
NOTES.VMS
NOTES.WIN
README.ENGINE
README.FIPS
README.md
SUPPORT.md
VERSION

openssl logo

travis badge appveyor badge

Welcome to the OpenSSL Project

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.

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 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.

Since 2016, development takes place in public on the GitHub open source platform. The OpenSSL Project Pages at openssl.github.io are a valuable source of information if you want to get familiar with our development process on GitHub.

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

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

All rights reserved.