Go to file
Matt Caswell 7f9822a482 Add blinding to a DSA signature
This extends the recently added ECDSA signature blinding to blind DSA too.

This is based on side channel attacks demonstrated by Keegan Ryan (NCC
Group) for ECDSA which are likely to be able to be applied to DSA.

Normally, as in ECDSA, during signing the signer calculates:

s:= k^-1 * (m + r * priv_key) mod order

In ECDSA, the addition operation above provides a sufficient signal for a
flush+reload attack to derive the private key given sufficient signature
operations.

As a mitigation (based on a suggestion from Keegan) we add blinding to
the operation so that:

s := k^-1 * blind^-1 (blind * m + blind * r * priv_key) mod order

Since this attack is a localhost side channel only no CVE is assigned.

This commit also tweaks the previous ECDSA blinding so that blinding is
only removed at the last possible step.

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/6522)
2018-06-21 10:15:57 +01:00
.github
apps openssl ca: open the output file as late as possible 2018-06-21 06:56:23 +02:00
boringssl@2070f8ad91
Configurations Improve the output of make doc-nits 2018-06-19 17:13:03 +02:00
crypto Add blinding to a DSA signature 2018-06-21 10:15:57 +01:00
demos Update certificates in demos/bio, demos/cms, demos/smime 2018-06-15 09:10:30 +10:00
doc Fix spelling errors in documentation. 2018-06-21 14:54:27 +10:00
engines Update copyright year 2018-05-01 13:34:30 +01:00
external/perl
fuzz New GOST identificators 2018-06-08 12:06:40 -04:00
include Prepare for 1.1.1-pre9-dev 2018-06-20 15:49:35 +01:00
krb5@b9ad6c4950
ms Update copyright year 2018-05-01 13:34:30 +01:00
os-dep
pyca-cryptography@95820b4e4f update pyca/cryptography submodule 2018-06-20 14:34:47 +01:00
ssl Fix enable-ssl3 enable-ssl3-method 2018-06-19 18:21:38 +01:00
test Update copyright year 2018-06-20 15:29:23 +01:00
tools
util Update copyright year 2018-06-20 15:29:23 +01:00
VMS
.gitattributes
.gitignore
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml .travis.yml: give make update exit code meaning again 2018-06-12 12:31:45 +02:00
ACKNOWLEDGEMENTS
appveyor.yml CI config: no need to make both install and install_docs 2018-05-14 17:51:48 +02:00
AUTHORS
build.info Configurations/10-main.conf: replace -bexpall with explicit list on AIX. 2018-06-13 10:48:27 +02:00
CHANGES Add blinding to a DSA signature 2018-06-21 10:15:57 +01:00
config Configure: move --noexecstack probe to Configure. 2018-05-05 20:44:56 +02:00
config.com
Configure Configure: add shared() to facilitate shared-specific flags. 2018-06-13 10:47:43 +02:00
CONTRIBUTING Add a note on CHANGES and NEWS in CONTRIBUTING 2018-05-17 13:51:11 +02:00
e_os.h
FAQ
INSTALL Document no-sm2 2018-06-21 10:14:06 +01:00
LICENSE
NEWS
NOTES.ANDROID NOTES.ANDROID: fix typo in build notes 2018-05-15 21:22:41 +02:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX NOTES.UNIX: expand the description of RPATHs 2018-06-20 22:38:57 +02:00
NOTES.VMS
NOTES.WIN
README Prepare for 1.1.1-pre9-dev 2018-06-20 15:49:35 +01:00
README.ENGINE
README.FIPS

 OpenSSL 1.1.1-pre9-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.