Go to file
Kurt Roeckx ea6199ea91 conf fuzzer: also check for an empty file
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>

GH: #1828
2016-11-03 05:13:34 +01:00
.github Add a github pull request template 2016-10-22 14:53:11 +02:00
apps Add the SSL_METHOD for TLSv1.3 and all other base changes required 2016-11-02 13:08:21 +00:00
Configurations Link using -znodelete 2016-11-02 23:32:50 +00:00
crypto Implement GET_MODULE_HANDLE_EX_FLAG_PIN for windows 2016-11-02 23:32:50 +00:00
demos Crude VMS build files for demos/bio/ 2016-09-20 18:24:24 +02:00
doc Add documentation for DTLS_get_data_mtu() 2016-11-02 14:00:12 +00:00
engines Fix some style issues in ossltest 2016-11-02 13:28:21 +00:00
external/perl
fuzz conf fuzzer: also check for an empty file 2016-11-03 05:13:34 +01:00
include Add a DSO_dsobyaddr() function 2016-11-02 23:32:50 +00:00
ms Revert "RT4526: Call TerminateProcess, not ExitProcess" 2016-06-16 17:37:37 +01:00
os-dep Move Haiku configuration to separate config file to denote 2016-05-19 22:39:52 +02:00
ssl Fail if an unrecognised record type is received 2016-11-02 23:22:48 +00:00
test Add a test to dynamically load and unload the libraries 2016-11-02 23:32:50 +00:00
tools Add -h and -help for c_rehash script and app 2016-09-14 08:59:48 -04:00
util Add a DSO_dsobyaddr() function 2016-11-02 23:32:50 +00:00
VMS VMS: Don't force symbol mixed case when building DSOs 2016-09-11 23:18:03 +02:00
.gitattributes crypto/pkcs12: facilitate accessing data with non-interoperable password. 2016-08-22 13:52:59 +02:00
.gitignore Don't ignore Makefiles in demos/ 2016-09-20 18:24:24 +02:00
.travis-create-release.sh
.travis.yml Secure our notification email. 2016-11-02 01:58:59 +01:00
ACKNOWLEDGEMENTS
appveyor.yml Correct installation test in appveyor 2016-10-21 13:46:49 +02:00
AUTHORS
build.info Have the VMS shared library file names contain the shared version 2016-07-02 15:49:45 +02:00
CHANGES Add a CHANGES entry for the unrecognised record type change 2016-11-02 23:22:48 +00:00
config Fix support for DragonFly BSD 2016-10-22 04:25:17 -04:00
config.com VMS: no ENDIF on one line IF statements, in config.com 2016-08-17 10:48:43 +02:00
Configure Update Configure to know about tls1_3 2016-11-02 13:08:21 +00:00
CONTRIBUTING Fix grammar-o in CONTRIBUTING 2016-11-01 12:32:11 -04:00
e_os.h Change default directory for the .rnd file on Windows and VMS 2016-06-20 11:06:40 +02:00
FAQ
INSTALL Update Configure to know about tls1_3 2016-11-02 13:08:21 +00:00
LICENSE
Makefile.shared HPUX: Add the forgotten $(DSTDIR) when linking DSOs 2016-11-01 00:51:03 +01:00
NEWS Updates CHANGES and NEWS for new release 2016-09-26 10:24:37 +01:00
NOTES.DJGPP Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
NOTES.PERL Tweaks to NOTES.PERL 2016-06-03 17:10:16 +01:00
NOTES.VMS Add a note about a perl issue on VMS and how to work around it 2016-08-06 16:00:13 +02:00
NOTES.WIN Fix typo 2016-10-14 10:01:54 +01:00
README Fix typo (reported by Matthias St. Pierre) 2016-10-26 11:48:43 -04:00
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.