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.
Ben Laurie e64b555781 ok was uninitialised on failure. 6 years ago
Configurations ARMv8 assembly pack: add OPENSSL_cleanse. 6 years ago
VMS Fix VMS/openssl_{startup,shutddown}.com.in 6 years ago
apps Make it possible to have RFC2254 escapes with ASN1_STRING_print_ex() 6 years ago
crypto ok was uninitialised on failure. 6 years ago
demos Consolidate copyright for demos 6 years ago
doc When strict SCT fails record verification failure 6 years ago
engines Add some check for malloc failure in the CAPI engine 6 years ago
external/perl Copyright consolidation; .pm and Configure 6 years ago
fuzz Add fuzzing! 6 years ago
include When strict SCT fails record verification failure 6 years ago
ms Copyright consolidation: perl files 6 years ago
ssl When strict SCT fails record verification failure 6 years ago
test Copyright consolidation 02/10 6 years ago
tools Remove --classic build entirely 6 years ago
util Small typo, a tab where there should have been a space 6 years ago
.gitattributes *.der files are binary. 6 years ago
.gitignore Replace cipherlist test 6 years ago
.travis-create-release.sh Remove the -n tar flag from osx dist creation 6 years ago
.travis.yml Try 'make install' with one of the Travis configurations 6 years ago
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 7 years ago
AUTHORS Copyright consolidation: perl files 6 years ago
CHANGES Unify <TYPE>_up_ref methods signature and behaviour. 6 years ago
CONTRIBUTING Recommend GH over RT, per team vote. 6 years ago
Configure Add support for RC / WINDRES env variables 6 years ago
FAQ Move FAQ to the web. 7 years ago
INSTALL VMS: support VERBOSE and V in descrip.mms 6 years ago
INSTALL.DJGPP DJGPP adjustments 6 years ago
INSTALL.WCE Refactor file writing - information on our use of Perl and Perl modules 7 years ago
LICENSE Copyright consolidation 07/10 6 years ago
Makefile.shared Add support for RC / WINDRES env variables 6 years ago
NEWS Manual fixes after copyright consolidation 6 years ago
NOTES.VMS Force argv to be an array of long pointers on VMS 6 years ago
NOTES.WIN Windows: Add CRYPT32.LIB to the libraries to link you app with 6 years ago
README Prepare for 1.1.0-pre6-dev 6 years ago
README.ECC Add NSA sublicense info. 11 years ago
README.ENGINE Remove Ubsec engine 6 years ago
README.FIPS Remove more (rest?) of FIPS build stuff. 7 years ago
README.PERL README.PERL: clarify "matching" Perl requirement on Windows. 6 years ago
appveyor.yml Update Travis and Appveyor for change to shared by default 6 years ago
build.info Build system: VC-WIN64I fixups. 6 years ago
config Add a case for 64-bit OS X in config 6 years ago
config.com Harmonize the option processing in 'config' and 'config.com' 6 years ago
e_os.h Manual fixes after copyright consolidation 6 years ago


OpenSSL 1.1.0-pre6-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
Secure Sockets Layer (SSLv3) and Transport Layer Security (TLS) protocols as
well as a full-strength general purpose cryptographic library. The project is
managed by a worldwide community of volunteers that use the Internet to
communicate, plan, and develop the OpenSSL toolkit and its related

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


See the OpenSSL website www.openssl.org for details on how to obtain
commercial technical support.

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

- Download the current snapshot from ftp://ftp.openssl.org/snapshot/
to see if the problem has already been addressed
- Remove ASM versions of libraries
- Remove compiler optimisation flags

If you wish to report a bug then please include the following information in
any bug report:

- On Unix systems:
Self-test report generated by 'make report'
- On other systems:
OpenSSL version: output of 'openssl version -a'
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)

Email the report to:


In order to avoid spam, this is a moderated mailing list, and it might
take a day for the ticket to show up. (We also scan posts to make sure
that security disclosures aren't publically posted by mistake.) Mail
to this address is recorded in the public RT (request tracker) database
(see https://www.openssl.org/community/index.html#bugs for details) and
also forwarded the public openssl-dev mailing list. Confidential mail
may be sent to openssl-security@openssl.org (PGP key available from the
key servers).

Please do NOT use this for general assistance or support queries.
Just because something doesn't work the way you expect does not mean it
is necessarily a bug in OpenSSL.

You can also make GitHub pull requests. If you do this, please also send
mail to rt@openssl.org with a link to the PR so that we can more easily
keep track of it.




A number of nations, in particular the U.S., 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.