TLS/SSL and crypto library
Find a file
Richard Levitte 6bb2106e24 Add the generate mechanism from unixmake to unix-Makefile.tmpl
Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-02-11 20:10:44 +01:00
apps Remove TLS heartbeat, disable DTLS heartbeat 2016-02-11 12:57:26 -05:00
certs Fix verify(1) to report failure when verification fails 2016-01-13 17:55:17 -05:00
Configurations Add the generate mechanism from unixmake to unix-Makefile.tmpl 2016-02-11 20:10:44 +01:00
crypto Move to REF_DEBUG, for consistency. 2016-02-11 12:40:32 -05:00
demos GH601: Various spelling fixes. 2016-02-05 15:25:50 -05:00
doc Hide OPENSSL_INIT_SETTINGS. 2016-02-11 08:43:46 -05:00
engines Test for and use AES CSP for RSA if present. 2016-02-11 16:01:44 +00:00
external/perl Change the transfer perl module so the real module gets properly registered 2016-02-04 19:44:03 +01:00
include Remove TLS heartbeat, disable DTLS heartbeat 2016-02-11 12:57:26 -05:00
ms ms/uplink-x86.pl: make it work. 2016-02-10 12:53:25 +01:00
Netware GH601: Various spelling fixes. 2016-02-05 15:25:50 -05:00
os2 Make a number of changes to the OS/2 build. Submitter's comment below. 2003-11-28 14:51:30 +00:00
ssl Don't check self signed certificate signature security. 2016-02-11 19:00:41 +00:00
test Remove TLS heartbeat, disable DTLS heartbeat 2016-02-11 12:57:26 -05:00
tools unified build scheme: add build.info files 2016-02-01 12:46:58 +01:00
util Don't add filename comment. 2016-02-11 13:36:14 -05:00
VMS clean away old VMS cruft 2016-02-10 14:36:32 +01:00
.gitignore Templatize util/domd 2016-01-29 16:56:07 -05:00
.travis-create-release.sh Configure first in travis create release 2016-01-26 08:26:27 +01:00
.travis.yml unified build scheme: add instructions for travis to build with --unified 2016-02-10 14:36:04 +01:00
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 2015-12-08 16:07:09 -05:00
appveyor.yml Add initial AppVeyor configuration 2015-11-21 18:06:31 +01:00
build.info unified build scheme: add a "unified" template for VMS descrip.mms 2016-02-10 14:36:32 +01:00
CHANGES Remove TLS heartbeat, disable DTLS heartbeat 2016-02-11 12:57:26 -05:00
config unified build scheme: a first introduction 2016-02-01 12:46:58 +01:00
config.com unified build scheme: add a "unified" template for VMS descrip.mms 2016-02-10 14:36:32 +01:00
Configure Remove TLS heartbeat, disable DTLS heartbeat 2016-02-11 12:57:26 -05:00
CONTRIBUTING Ask for tests in CONTRIBUTING 2016-01-25 17:12:57 -05:00
e_os.h Move to REF_DEBUG, for consistency. 2016-02-11 12:40:32 -05:00
FAQ Move FAQ to the web. 2015-08-16 19:02:29 -04:00
GitConfigure Remove remaining variables for symlinked/copied headers and tests 2015-03-31 20:16:01 +02:00
GitMake Build on MacOS. 2014-02-09 12:49:04 +00:00
INSTALL Updates for auto init/deinit review comments 2016-02-09 15:12:02 +00:00
INSTALL.DJGPP Refactor file writing - information on our use of Perl and Perl modules 2016-01-22 23:12:22 +01:00
INSTALL.NW misspellings fixes by https://github.com/vlajos/misspell_fixer 2013-09-05 21:39:42 +01:00
INSTALL.OS2 Add support for shared libraries with OS/2. 2002-07-17 13:27:43 +00:00
INSTALL.VMS unified build scheme: rewrite INSTALL.VMS 2016-02-10 14:36:32 +01:00
INSTALL.WCE Refactor file writing - information on our use of Perl and Perl modules 2016-01-22 23:12:22 +01:00
INSTALL.WIN Updates for auto init/deinit review comments 2016-02-09 15:12:02 +00:00
LICENSE Update license year range to 2016 2016-01-19 10:24:05 -05:00
Makefile.in Move to REF_DEBUG, for consistency. 2016-02-11 12:40:32 -05:00
Makefile.shared Make util/mkrc.pl location agnostic and adapt Makefile.shared 2016-02-11 17:08:38 +01:00
NEWS unified build system: add CHANGES & NEWS 2016-02-10 14:41:43 +01:00
openssl.doxy Add functions to add certs to stacks, used for CA file/path stuff in servers. 1999-02-28 17:41:55 +00:00
openssl.spec Simplify and update openssl.spec 2013-11-30 14:11:05 +00:00
PROBLEMS Fixing typo in PROBLEMS 2015-09-27 20:50:40 -04:00
README Fix typos 2016-01-27 12:08:11 -05:00
README.ECC Add NSA sublicense info. 2011-05-11 12:50:57 +00:00
README.ENGINE oops, there were other cases of "ENGINE_ID" to change too. 2002-07-08 15:16:10 +00:00
README.FIPS Remove more (rest?) of FIPS build stuff. 2016-01-06 12:07:26 -05:00
README.PERL Change the VMS perl pointer from SF file store to the project page 2016-02-10 22:25:48 +01:00

 OpenSSL 1.1.0-pre3-dev

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

 DESCRIPTION
 -----------

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

 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.

 OVERVIEW
 --------

 The OpenSSL toolkit includes:

 libssl.a:
     Provides the client and server-side implementations for SSLv3 and TLS.

 libcrypto.a:
     Provides general cryptographic and X.509 support needed by SSL/TLS but
     not logically part of it.

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

 INSTALLATION
 ------------

 See the appropriate file:
        INSTALL         Linux, Unix, etc.
        INSTALL.DJGPP   DOS platform with DJGPP
        INSTALL.NW      Netware
        INSTALL.OS2     OS/2
        INSTALL.VMS     VMS
        INSTALL.WIN     Windows
        INSTALL.WCE     Windows CE

 SUPPORT
 -------

 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
 first:

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

    rt@openssl.org

 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.

 HOW TO CONTRIBUTE TO OpenSSL
 ----------------------------

 See CONTRIBUTING

 LEGALITIES
 ----------

 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.