Go to file
Viktor Dukhovni 6e32825631 Check Suite-B constraints with EE DANE records
When DANE-EE(3) matches or either of DANE-EE/PKIX-EE fails, we don't
build a chain at all, but rather succeed or fail with just the leaf
certificate.  In either case also check for Suite-B violations.

As unlikely as it may seem that anyone would enable both DANE and
Suite-B, we should do what the application asks.

Took the opportunity to eliminate the "cb" variables in x509_vfy.c,
just call ctx->verify_cb(ok, ctx)

Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
2016-01-20 18:59:46 -05:00
apps Remove update tags 2016-01-20 09:09:14 -05:00
certs Fix verify(1) to report failure when verification fails 2016-01-13 17:55:17 -05:00
Configurations Add some extra Cygwin targets as aliases for Cygwin-x86 2016-01-18 16:16:00 +01:00
crypto Check Suite-B constraints with EE DANE records 2016-01-20 18:59:46 -05:00
demos Consolidate "make update" 2016-01-20 09:09:14 -05:00
doc Add documentation for EVP_PKEY_TLS1_PRF 2016-01-19 14:00:33 +00:00
engines Remove update tags 2016-01-20 09:09:14 -05:00
include Handle SSL_shutdown while in init more appropriately 2016-01-20 13:58:12 +00:00
ms Fix various windows compilation issues 2015-01-28 22:55:15 +00:00
Netware
os2
ssl Remove update tags 2016-01-20 09:09:14 -05:00
test Remove update tags 2016-01-20 09:09:14 -05:00
tools Remove update tags 2016-01-20 09:09:14 -05:00
util Remove the GOST engine 2016-01-19 22:29:32 +00:00
VMS Remove the old VMS linker option file creator for shlibs 2016-01-07 21:09:43 +01:00
.gitignore Move Makefiles to Makefile.in 2016-01-12 16:26:56 -05:00
.travis-create-release.sh Move Makefiles to Makefile.in 2016-01-12 16:26:56 -05:00
.travis.yml Adapt the OS X build to use the OS X tar 2015-12-08 21:04:53 +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
CHANGES Remove the GOST engine 2016-01-19 22:29:32 +00:00
config Adjust the configuration target name from Cygwin-i686 to Cygwin-x86 2016-01-18 16:16:00 +01:00
Configure Refactor config - split read_config into read_config and resolve_config 2016-01-20 22:07:59 +01:00
CONTRIBUTING Clarify the preferred way of creating patch files 2015-11-02 14:32:16 +00:00
e_os.h Add a no-egd option to disable EGD-related code 2016-01-14 13:02:51 -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
INSTALL Update Windows installation instructions 2016-01-15 11:01:00 +00:00
install.com
INSTALL.DJGPP
INSTALL.NW
INSTALL.OS2
INSTALL.VMS Add a few notes on perl 2015-09-15 13:14:49 +02:00
INSTALL.WCE Update Windows installation instructions 2016-01-15 11:01:00 +00:00
INSTALL.WIN Update Windows installation instructions 2016-01-15 11:01:00 +00:00
LICENSE Update license year range to 2016 2016-01-19 10:24:05 -05:00
Makefile.in Consolidate "make update" 2016-01-20 09:09:14 -05:00
Makefile.shared Don't strip object files on Cygwin 2016-01-18 16:16:00 +01:00
makevms.com Fix DES_LONG breakage 2016-01-13 12:37:48 -05:00
NEWS Editorial 2016-01-14 12:27:57 -05:00
openssl.doxy
openssl.spec
PROBLEMS Fixing typo in PROBLEMS 2015-09-27 20:50:40 -04:00
README Update Windows installation instructions 2016-01-15 11:01:00 +00:00
README.ECC
README.ENGINE
README.FIPS Remove more (rest?) of FIPS build stuff. 2016-01-06 12:07:26 -05: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 cryptograpic 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.