Go to file
Matt Caswell d23adad113 EVP_CIPHER_CTX_set_keylen should not succeed if a bad keylen is passed
EVP_CIPHER_CTX_set_keylen() was succeeding even though a bad key length
is passed to it. This is because the set_ctx_params() were all accepting
this parameter and blindly changing the keylen even though the cipher did
not accept a variable key length. Even removing this didn't entirely
resolve the issue because set_ctx_params() functions succeed even if
passed a parameter they do not recognise.

This should fix various issues found by OSSfuzz/Cryptofuzz.

Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/10449)
2019-11-19 13:33:54 +00:00
.github
apps commit a6efbe123af3d98b4d10d4fcdfe68dc5303212f8 2019-11-16 08:29:26 +10:00
boringssl@2070f8ad91
Configurations Configuration: make Solaris builds with gcc recognise GNU ld 2019-11-10 04:58:08 +01:00
crypto EVP_CIPHER_CTX_set_keylen should not succeed if a bad keylen is passed 2019-11-19 13:33:54 +00:00
demos
doc Properties: make query cache reference count aware. 2019-11-18 18:51:26 +10:00
engines Update source files for deprecation at 3.0 2019-11-07 11:37:25 +01:00
external/perl
fuzz Update source files for deprecation at 3.0 2019-11-07 11:37:25 +01:00
include Properties: make query cache reference count aware. 2019-11-18 18:51:26 +10:00
krb5@b9ad6c4950
ms
os-dep
providers EVP_CIPHER_CTX_set_keylen should not succeed if a bad keylen is passed 2019-11-19 13:33:54 +00:00
pyca-cryptography@09403100de
ssl commit a6efbe123af3d98b4d10d4fcdfe68dc5303212f8 2019-11-16 08:29:26 +10:00
test Properties: make query cache reference count aware. 2019-11-18 18:51:26 +10:00
tools
util Add missing EVP_PKEY_METHOD accessors for digestsign and digestverify 2019-11-17 08:27:06 +01:00
VMS
.gitattributes
.gitignore Add confdump to .gitignore 2019-11-14 09:40:24 +00:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml travis.yml: add arch s390x target 2019-11-15 11:15:43 +01:00
ACKNOWLEDGEMENTS
appveyor.yml
AUTHORS
build.info
CHANGES Add a .pragma directive for configuration files 2019-11-12 13:33:12 +01:00
config
config.com
configdata.pm.in
Configure
CONTRIBUTING
e_os.h
FAQ
HACKING
INSTALL Update INSTALL to document the changed '--api' and 'no-deprecated' 2019-11-07 11:37:37 +01:00
LICENSE
NEWS
NOTES.ANDROID
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX
NOTES.VALGRIND
NOTES.VMS
NOTES.WIN
README
README.ENGINE
README.FIPS
VERSION

 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 the Apache License 2.0, which means
 that you are free to get and use it for commercial and non-commercial
 purposes as long as you fulfill its conditions.

 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.