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.
isnotnick ec5b56f3c5 RT3513: req doesn't display attributes using utf8string 7 years ago
Configurations Alpha assembly pack: make it work on Linux. 7 years ago
VMS Copyright consolidation: perl files 7 years ago
apps Handle no async jobs in libssl 7 years ago
crypto RT3513: req doesn't display attributes using utf8string 7 years ago
demos Remove --classic build entirely 7 years ago
doc Handle no async jobs in libssl 7 years ago
engines Remove obsolete defined(__INTEL__) condition. 7 years ago
external/perl Copyright consolidation; .pm and Configure 7 years ago
include Handle no async jobs in libssl 7 years ago
ms Copyright consolidation: perl files 7 years ago
ssl Move 3DES from HIGH to MEDIUM 7 years ago
test testlib/OpenSSL/Test.pm: address 5.10 warnings. 7 years ago
tools Remove --classic build entirely 7 years ago
util Tweak generated warning lines. 7 years ago
.gitattributes *.der files are binary. 7 years ago
.gitignore Add apps/tsget and test/ssltest_old to .gitignore 7 years ago
.travis-create-release.sh Remove the -n tar flag from osx dist creation 7 years ago
.travis.yml Try 'make install' with one of the Travis configurations 7 years ago
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 7 years ago
AUTHORS Copyright consolidation: perl files 7 years ago
CHANGES Move 3DES from HIGH to MEDIUM 7 years ago
CONTRIBUTING Ask for tests in CONTRIBUTING 7 years ago
Configure Add the possibility for local build file templates 7 years ago
FAQ Move FAQ to the web. 7 years ago
INSTALL Remove the never-functional no-sct 7 years ago
INSTALL.DJGPP Refactor file writing - information on our use of Perl and Perl modules 7 years ago
INSTALL.WCE Refactor file writing - information on our use of Perl and Perl modules 7 years ago
LICENSE Update license year range to 2016 7 years ago
Makefile.shared Add Haiku support. 7 years ago
NEWS Update CHANGES and NEWS for the new release 7 years ago
NOTES.VMS Force argv to be an array of long pointers on VMS 7 years ago
NOTES.WIN Remove mk1mf documentation 7 years ago
README Prepare for 1.1.0-pre6-dev 7 years ago
README.ECC Add NSA sublicense info. 12 years ago
README.ENGINE Remove Ubsec engine 7 years ago
README.FIPS Remove more (rest?) of FIPS build stuff. 7 years ago
README.PERL README.PERL: clarify "matching" Perl requirement on Windows. 7 years ago
appveyor.yml Update Travis and Appveyor for change to shared by default 7 years ago
build.info Build system: VC-WIN64I fixups. 7 years ago
config Add Haiku support. 7 years ago
config.com Harmonize the option processing in 'config' and 'config.com' 7 years ago
e_os.h Include winsock2.h even if compiling no-sock 7 years ago
openssl.spec GH781: openssl.spec: use secure urls 7 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.