Go to file
Matt Caswell c9fe362303 Correct value for BN_security_bits()
The function BN_security_bits() uses the values from SP800-57 to assign
security bit values for different FF key sizes. However the value for 192
security bits is wrong. SP800-57 has it as 7680 but the code had it as
7690.

Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4546)
2017-10-23 14:00:26 +01:00
.github
apps apps/s_client.c: add missing null check 2017-10-22 21:31:20 +02:00
boringssl@2070f8ad91
Configurations Remove email addresses from source code. 2017-10-13 10:06:59 -04:00
crypto Correct value for BN_security_bits() 2017-10-23 14:00:26 +01:00
demos
doc ECDSA_* is deprecated. EC_KEY_* is used instead 2017-10-20 16:13:28 +02:00
engines Add predicatable RAND_METHOD to test ENGINE 2017-08-06 19:24:32 +01:00
external/perl
fuzz Remove unused variable. 2017-10-16 15:18:24 -04:00
include Remove parentheses of return. 2017-10-18 16:05:06 +01:00
krb5@b9ad6c4950
ms Remove an unused file 2017-10-11 15:32:23 +01:00
os-dep
pyca-cryptography@c1f8e46033 Update pyca-cryptography to latest commit 2017-08-11 11:16:44 +10:00
ssl Various clean-ups 2017-10-20 22:58:46 -04:00
test Fix reseeding issues of the public RAND_DRBG 2017-10-18 08:39:20 -05:00
tools
util Additional name for all commands 2017-10-18 15:33:56 -04:00
VMS
.gitattributes
.gitignore Reduce the things we ignore in test/ 2017-10-09 17:58:50 +02:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh
.travis.yml Add branch coverage to coveralls statistics 2017-10-16 06:26:30 +02:00
ACKNOWLEDGEMENTS
appveyor.yml
AUTHORS
build.info
CHANGES Rewrite some code 2017-10-07 11:26:35 -04:00
config Remove some commented out code 2017-10-05 10:13:25 +01:00
config.com
Configure Configure: add -Wmisleading-indentation to strict warnings flags. 2017-09-22 22:08:35 +02:00
CONTRIBUTING
e_os.h e_os.h: add prandom and hwrng to the list of random devices on s390x. 2017-10-22 22:56:18 +02:00
FAQ
INSTALL Fix description of how to report a bug in INSTALL 2017-08-25 14:16:20 +01:00
LICENSE
Makefile.shared
NEWS
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX
NOTES.VMS
NOTES.WIN
README
README.ECC
README.ENGINE
README.FIPS

 OpenSSL 1.1.1-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
 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 optimisation 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'
    - Any "Configure" options that you selected during compilation of the
      library if applicable (see INSTALL)
    - 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.