Go to file
Kurt Roeckx 7e999d5101 Fix duplicate error codes
Reviewed-by: Matt Caswell <matt@openssl.org>
GH: #2732
2017-02-23 23:12:31 +01:00
.github
apps Check for the presence of _WIN32 rather than its value. 2017-02-23 14:41:20 +01:00
boringssl@490469f850
Configurations appveyor.yml: engage VC-WIN64A-masm. 2017-02-21 22:39:00 +01:00
crypto Fix typo, should be && rather than & 2017-02-22 21:07:28 +01:00
demos
doc Add SSL_CTX early callback 2017-02-23 19:40:26 +01:00
engines
external/perl
fuzz Update client, server and x509 fuzz corpus 2017-02-21 18:53:07 +01:00
include Fix duplicate error codes 2017-02-23 23:12:31 +01:00
ms
os-dep
ssl Implement SSL_read_ex() and SSL_write_ex() as documented. 2017-02-23 20:40:05 +01:00
test Add an sslapitest for early callback 2017-02-23 19:40:27 +01:00
tools
util Add SSL_CTX early callback 2017-02-23 19:40:26 +01:00
VMS
.gitattributes
.gitignore
.gitmodules
.travis-create-release.sh
.travis.yml .travis.yml: remove osx from build matrix. 2017-02-19 21:27:57 +01:00
ACKNOWLEDGEMENTS
appveyor.yml appveyor.yml: engage VC-WIN64A-masm. 2017-02-21 22:39:00 +01:00
AUTHORS
build.info
CHANGES
config Implementation of the ARIA cipher as described in RFC 5794. 2017-02-21 11:51:45 +01:00
config.com
Configure Remove -Wno-parentheses-equality from gcc --strict-warnings options. 2017-02-22 14:21:18 -05:00
CONTRIBUTING
e_os.h Revert "Use memcmp() instead of CRYPTO_memcmp() when fuzzing" 2017-02-20 18:54:39 +01:00
FAQ
INSTALL
LICENSE
Makefile.shared
NEWS
NOTES.DJGPP
NOTES.PERL
NOTES.VMS
NOTES.WIN
README
README.ECC
README.ENGINE
README.FIPS

 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.

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

 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.

 OVERVIEW
 --------

 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.

 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, Windows, OpenVMS, ...
        NOTES.*         INSTALL addendums for different platforms

 SUPPORT
 -------

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

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

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

 See CONTRIBUTING

 LEGALITIES
 ----------

 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.