Go to file
Pauli 4bed94f0c1 SHA512/224 and SHA512/256
Support added for these two digests, available only via the EVP interface.

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5093)
2018-01-24 07:09:46 +10:00
.github Remind people to have 'Fixes #XXXX' in the commit message 2017-04-02 21:51:47 +02:00
Configurations Don't add $(EX_LIBS) to libssl.pc's Libs.private 2018-01-23 13:55:48 +01:00
VMS Simplify the handling of shared library version numbers 2017-07-26 22:53:03 +02:00
apps Fix no-ec --strict-warnings builds 2018-01-23 08:59:28 -06:00
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 2017-03-14 12:12:13 +00:00
crypto SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
demos Add "friendly name" extractor 2017-11-30 14:53:46 -05:00
doc SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
engines Copyright update of more files that have changed this year 2018-01-19 13:34:03 +01:00
external/perl
fuzz SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
include SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
krb5@b9ad6c4950 [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
ms Many spelling fixes/typo's corrected. 2017-11-11 19:03:10 -05:00
os-dep
pyca-cryptography@c1f8e46033 Update pyca-cryptography to latest commit 2017-08-11 11:16:44 +10:00
ssl Move fprintf after assignment to avoid crash. 2018-01-22 15:14:40 -05:00
test SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
tools
util SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
.gitattributes
.gitignore Remove test-runs dir, adjust .gitignore 2017-12-15 19:27:42 +01:00
.gitmodules [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
.travis-apt-pin.preferences Fix travis clang-3.9 builds 2017-06-23 17:57:02 +01:00
.travis-create-release.sh
.travis.yml Enable the ARIA ciphers by default. 2017-12-18 08:49:53 +10:00
ACKNOWLEDGEMENTS
AUTHORS
CHANGES SHA512/224 and SHA512/256 2018-01-24 07:09:46 +10:00
CONTRIBUTING
Configure Copyright update of more files that have changed this year 2018-01-19 13:34:03 +01:00
FAQ
INSTALL Document how the configuration option 'reconf' works 2017-12-08 00:36:21 +01:00
LICENSE Update the license end year 2018-01-20 10:02:23 +01:00
NEWS Update CHANGES and NEWS for new release 2017-12-06 15:44:39 +00:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX
NOTES.VMS More typo fixes 2017-03-29 07:14:29 +02:00
NOTES.WIN Various doc fixes. 2017-07-26 23:09:40 -04:00
README Many spelling fixes/typo's corrected. 2017-11-11 19:03:10 -05:00
README.ECC
README.ENGINE Remove bsd_cryptodev engine 2017-06-19 09:31:45 -04:00
README.FIPS
appveyor.yml Remove notification settings from appveyor.yml 2017-05-17 12:36:28 +02:00
build.info VMS build.info: uppercase args to perl modules must be quoted 2017-12-18 07:49:53 +01:00
config Make sure ./config passes options to ./Configure correctly 2017-12-08 00:36:21 +01:00
config.com
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

README

 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 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'
    - 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.