A local copy of OpenSSL from GitHub
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Johannes Bauer e65f650922 Set error when HKDF used without parameters 5 years ago
.github Remind people to have 'Fixes #XXXX' in the commit message 5 years ago
Configurations Simplify the handling of shared library version numbers 5 years ago
VMS Simplify the handling of shared library version numbers 5 years ago
apps Add '-ext' option to display extensions in 'x509' 5 years ago
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 5 years ago
crypto Set error when HKDF used without parameters 5 years ago
demos Demo style fixes and modernisation. 5 years ago
doc Add EC key generation paragraph in doc/HOWTO/keys.txt 5 years ago
engines Cleanup some copyright stuff 5 years ago
external/perl Copyright consolidation; .pm and Configure 6 years ago
fuzz Install custom RAND_METHOD for fuzzing 5 years ago
include Set error when HKDF used without parameters 5 years ago
krb5@b9ad6c4950 [extended tests] Enable krb5 tests in Travis 5 years ago
ms Remove filename argument to x86 asm_init. 5 years ago
os-dep Move Haiku configuration to separate config file to denote 6 years ago
pyca-cryptography@139b25f2ba Update the pyca-cryptography version 5 years ago
ssl Fix new_session_cb calls in TLSv1.3 5 years ago
test Simplify some of the sslapitest code. 5 years ago
tools Add -h and -help for c_rehash script and app 6 years ago
util make update 5 years ago
.gitattributes crypto/pkcs12: facilitate accessing data with non-interoperable password. 6 years ago
.gitignore Add apps/progs.h to gitignore 5 years ago
.gitmodules [extended tests] Enable krb5 tests in Travis 5 years ago
.travis-apt-pin.preferences Fix travis clang-3.9 builds 5 years ago
.travis-create-release.sh Remove the -n tar flag from osx dist creation 6 years ago
.travis.yml Add echo for end of each build phase 5 years ago
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 7 years ago
AUTHORS Copyright consolidation: perl files 6 years ago
CHANGES Wire SHA3 EVPs and add tests. 5 years ago
CONTRIBUTING Update the location of the pod files 6 years ago
Configure Perl: Use File::Glob::bsd_glob rather than File::Glob::glob 5 years ago
FAQ Move FAQ to the web. 7 years ago
INSTALL drop some no-longer-relevant TODO(TLS1.3) entries 5 years ago
LICENSE Update year, wording tweak 5 years ago
Makefile.shared Makefile.shared: Make link_shlib.linux-shared less verbose again 5 years ago
NEWS STORE: Add an entry in NEWS and CHANGES 5 years ago
NOTES.DJGPP Slight cleanup of the collection of READMEs, INSTALLs and NOTES 6 years ago
NOTES.PERL Tweaks to NOTES.PERL 6 years ago
NOTES.UNIX Add NOTES.UNIX, with a description on how to deal with runpaths 5 years ago
NOTES.VMS More typo fixes 5 years ago
NOTES.WIN Various doc fixes. 5 years ago
README Fix typo (reported by Matthias St. Pierre) 6 years ago
README.ECC Add NSA sublicense info. 11 years ago
README.ENGINE Remove bsd_cryptodev engine 5 years ago
README.FIPS Remove more (rest?) of FIPS build stuff. 7 years ago
appveyor.yml Remove notification settings from appveyor.yml 5 years ago
build.info Simplify the handling of shared library version numbers 5 years ago
config Better way to recognise mingw64 in config script 5 years ago
config.com VMS: no ENDIF on one line IF statements, in config.com 6 years ago
e_os.h Use randomness not entropy 5 years ago


OpenSSL 1.1.1-dev

Copyright (c) 1998-2016 The OpenSSL Project
Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
All rights reserved.


The OpenSSL Project is a collaborative effort to develop a robust,
commercial-grade, fully featured, and Open Source toolkit implementing the
Transport Layer Security (TLS) protocols (including SSLv3) as well as a
full-strength general purpose cryptographic library.

OpenSSL is descended from the SSLeay library developed by Eric A. Young
and Tim J. Hudson. The OpenSSL toolkit is licensed under a dual-license (the
OpenSSL license plus the SSLeay license), which means that you are free to
get and use it for commercial and non-commercial purposes as long as you
fulfill the conditions of both licenses.


The OpenSSL toolkit includes:

libssl (with platform specific naming):
Provides the client and server-side implementations for SSLv3 and TLS.

libcrypto (with platform specific naming):
Provides general cryptographic and X.509 support needed by SSL/TLS but
not logically part of it.

A command line tool that 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...


See the appropriate file:
INSTALL Linux, Unix, Windows, OpenVMS, ...
NOTES.* INSTALL addendums for different platforms


See the OpenSSL website www.openssl.org for details on how to obtain
commercial technical support. Free community support is available through the
openssl-users email list (see
https://www.openssl.org/community/mailinglists.html for further details).

If you have any problems with OpenSSL then please take the following steps

- Download the latest version from the repository
to see if the problem has already been addressed
- Configure with no-asm
- Remove compiler optimisation flags

If you wish to report a bug then please include the following information
and create an issue on GitHub:

- OpenSSL version: output of 'openssl version -a'
- Any "Configure" options that you selected during compilation of the
library if applicable (see INSTALL)
- OS Name, Version, Hardware platform
- Compiler Details (name, version)
- Application Details (name, version)
- Problem Description (steps that will reproduce the problem, if known)
- Stack Traceback (if the application dumps core)

Just because something doesn't work the way you expect does not mean it
is necessarily a bug in OpenSSL. Use the openssl-users email list for this type
of query.




A number of nations restrict the use or export of cryptography. If you
are potentially subject to such restrictions you should seek competent
professional legal advice before attempting to develop or distribute
cryptographic code.