Go to file
Matt Caswell 9fb6cb810b Fix bug where early_data does not work if no SNI callback is present
Fixes #4496

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Ben Kaduk <kaduk@mit.edu>
(Merged from https://github.com/openssl/openssl/pull/4519)
2017-10-12 15:19:49 +01:00
.github Remind people to have 'Fixes #XXXX' in the commit message 2017-04-02 21:51:47 +02:00
apps apps/speed.c: add 'rand' algo to enable DRBG performance measurements. 2017-10-10 09:24:52 -04:00
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 2017-03-14 12:12:13 +00:00
Configurations Use the possibility to have test results in a different directory 2017-10-09 17:57:13 +02:00
crypto make update 2017-10-12 02:41:27 +01:00
demos Demo style fixes and modernisation. 2017-07-13 07:34:40 +10:00
doc Add RFC7919 documentation. 2017-10-12 02:40:30 +01:00
engines Add predicatable RAND_METHOD to test ENGINE 2017-08-06 19:24:32 +01:00
external/perl
fuzz Stack sorting safety 2017-09-18 12:17:18 +10:00
include make update 2017-10-12 02:41:27 +01:00
krb5@b9ad6c4950 [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
ms Remove an unused file 2017-10-11 15:32:23 +01:00
os-dep
pyca-cryptography@c1f8e46033 Update pyca-cryptography to latest commit 2017-08-11 11:16:44 +10:00
ssl Fix bug where early_data does not work if no SNI callback is present 2017-10-12 15:19:49 +01:00
test Add RFC7919 tests. 2017-10-12 02:40:30 +01:00
tools
util make update 2017-10-12 02:41:27 +01:00
VMS Simplify the handling of shared library version numbers 2017-07-26 22:53:03 +02:00
.gitattributes
.gitignore Reduce the things we ignore in test/ 2017-10-09 17:58:50 +02:00
.gitmodules [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
.travis-apt-pin.preferences Fix travis clang-3.9 builds 2017-06-23 17:57:02 +01:00
.travis-create-release.sh
.travis.yml Add echo for end of each build phase 2017-07-04 16:23:59 -04:00
ACKNOWLEDGEMENTS
appveyor.yml Remove notification settings from appveyor.yml 2017-05-17 12:36:28 +02:00
AUTHORS
build.info Simplify the handling of shared library version numbers 2017-07-26 22:53:03 +02:00
CHANGES Rewrite some code 2017-10-07 11:26:35 -04:00
config Remove some commented out code 2017-10-05 10:13:25 +01:00
config.com
Configure Configure: add -Wmisleading-indentation to strict warnings flags. 2017-09-22 22:08:35 +02:00
CONTRIBUTING
e_os.h struct timeval include guards 2017-09-01 09:55:43 +10:00
FAQ
INSTALL Fix description of how to report a bug in INSTALL 2017-08-25 14:16:20 +01:00
LICENSE Update year, wording tweak 2017-02-28 10:13:32 -05:00
Makefile.shared Makefile.shared: Make link_shlib.linux-shared less verbose again 2017-07-24 11:57:44 +02:00
NEWS STORE: Add an entry in NEWS and CHANGES 2017-06-29 11:55:33 +02:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX Add NOTES.UNIX, with a description on how to deal with runpaths 2017-03-02 07:33:27 +01:00
NOTES.VMS More typo fixes 2017-03-29 07:14:29 +02:00
NOTES.WIN Various doc fixes. 2017-07-26 23:09:40 -04:00
README
README.ECC
README.ENGINE Remove bsd_cryptodev engine 2017-06-19 09:31:45 -04:00
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.