Go to file
Nicola Tuveri cf6404b141 [CMS] Test decryption of a ciphertext encrypted from 1.1.1
Current CMS en/decryption tests only validate that our current decyption
and encryption algorithms are compatible, but they say nothing about
correctness of the output for the given set of parameters.

As a partial fix in absence of proper KAT tests, we decrypt ciphertexts
generated with OpenSSL 1.1.1.

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/10631)
2020-02-18 19:11:10 +02:00
.github
apps Deprecate EC command line apps. 2020-02-18 19:53:52 +10:00
boringssl@2070f8ad91
Configurations TEST: Create test specific output directories 2020-02-18 09:45:51 +01:00
crypto [EC] Constify internal EC_KEY pointer usage 2020-02-18 19:11:10 +02:00
demos
doc DOC:Fix typos in x509v3_config.pod 2020-02-18 13:40:11 +01:00
engines Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
external/perl
fuzz Deprecate the low level DSA functions. 2020-02-12 08:52:41 +10:00
include chunk 7 of CMP contribution to OpenSSL 2020-02-17 07:43:58 +01:00
krb5@890ca2f401
ms
os-dep
providers [PROV][KEYMGMT][DH][DSA] use BN_clear_free for secrets 2020-02-18 19:11:10 +02:00
pyca-cryptography@09403100de
ssl Fix coverity issues 2020-02-14 07:28:46 +10:00
test [CMS] Test decryption of a ciphertext encrypted from 1.1.1 2020-02-18 19:11:10 +02:00
tools
util TEST: Optionally silence OpenSSL::Test::setup() 2020-02-18 09:45:53 +01:00
VMS
.gitattributes
.gitignore TEST: Create test specific output directories 2020-02-18 09:45:51 +01:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml Add a minimal build target for Travis and Appveyor 2020-02-11 13:22:39 +01:00
ACKNOWLEDGEMENTS
appveyor.yml Add a minimal build target for Travis and Appveyor 2020-02-11 13:22:39 +01:00
AUTHORS
build.info
CHANGES Deprecate EC command line apps. 2020-02-18 19:53:52 +10:00
config
config.com
configdata.pm.in
Configure Make secure-memory be a config option 2020-02-14 15:18:27 +01:00
CONTRIBUTING Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
e_os.h Make secure-memory be a config option 2020-02-14 15:18:27 +01:00
FAQ
HACKING
INSTALL
LICENSE
NEWS Add NEWS entry about deprecation of command line public tools 2020-02-12 08:52:42 +10:00
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.