TLS/SSL and crypto library
Find a file
Matt Caswell 8f50627402 Reject obviously invalid DSA parameters during signing
Fixes #8875

Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/8876)

(cherry picked from commit 9acbe07d23)
2019-05-07 16:54:31 +01:00
.github
apps openssl cms: add error message if operation option is missing 2019-05-02 23:06:43 +02:00
boringssl@2070f8ad91
Configurations Add RCFLAGS variable in Windows build file, and use it 2019-05-02 11:17:00 +02:00
crypto Reject obviously invalid DSA parameters during signing 2019-05-07 16:54:31 +01:00
demos Fix memory leaks in pkread.c demo file 2019-03-13 09:55:54 +00:00
doc man: fix a typo and a grammar nit in EVP_PKEY_meth_new(3) 2019-05-07 13:12:27 +02:00
engines Make the padlock engine build correctly 2019-02-27 11:34:40 +01:00
external/perl Update copyright year 2018-09-11 13:45:17 +01:00
fuzz Update copyright year 2018-11-20 13:27:36 +00:00
include Rework DSO API conditions and configuration option 2019-04-10 07:50:17 +02:00
krb5@b9ad6c4950
ms Update copyright year 2019-02-26 14:05:09 +00:00
os-dep
pyca-cryptography@09403100de Update the pyca-cryptography submodule 2018-09-10 12:04:03 +01:00
ssl Check if num is 0 before trying to malloc memory. Otherwise for client hellos without extensions SSL_client_hello_get1_extensions_present will return MALLOC_FAILURE. 2019-04-19 09:55:47 +01:00
test Test: use keywords instead of magic numbers for 'rsa_pss_saltlen' 2019-05-02 23:02:47 +02:00
tools
util Add a check for history section location to find-doc-nits 2019-04-15 12:26:49 +02:00
VMS
.gitattributes Don't export the submodules 'boringssl', 'krb5' and 'pyca-cryptography' 2018-11-24 18:43:54 +01:00
.gitignore Add a compile time test to verify that openssl/rsa.h and complex.h can 2018-09-17 09:44:45 +10:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh Remove all 'make dist' artifacts 2018-11-23 12:42:21 +01:00
.travis.yml .travis.yml: change -std=c89 to -ansi 2019-02-28 13:08:04 +01:00
ACKNOWLEDGEMENTS
appveyor.yml
AUTHORS
build.info
CHANGES Prepare for 1.1.1c-dev 2019-02-26 14:17:50 +00:00
config Update copyright year 2019-02-26 14:05:09 +00:00
config.com
Configure Allow setting RCFLAGS as Configure option or environment variable 2019-05-02 11:17:05 +02:00
CONTRIBUTING Remove unnecessary trailing whitespace 2019-02-05 16:29:17 +01:00
e_os.h Limit DEVRANDOM_WAIT to linux 2019-03-07 22:39:33 +01:00
FAQ
INSTALL Rework DSO API conditions and configuration option 2019-04-10 07:50:17 +02:00
LICENSE Update copyright year 2019-02-26 14:05:09 +00:00
NEWS Prepare for 1.1.1c-dev 2019-02-26 14:17:50 +00:00
NOTES.ANDROID Remove unnecessary trailing whitespace 2019-02-05 16:29:17 +01:00
NOTES.DJGPP Remove unnecessary trailing whitespace 2019-02-05 16:29:17 +01:00
NOTES.PERL
NOTES.UNIX
NOTES.VMS Remove unnecessary trailing whitespace 2019-02-05 16:29:17 +01:00
NOTES.WIN INSTALL,NOTES.WIN: classify no-asm as non-production option. 2018-07-25 15:47:12 +02:00
README Prepare for 1.1.1c-dev 2019-02-26 14:17:50 +00:00
README.ENGINE
README.FIPS

 OpenSSL 1.1.1c-dev

 Copyright (c) 1998-2018 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 optimization 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'
    - Configuration data: output of 'perl configdata.pm --dump'
    - 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.