Go to file
Theo Buehler c12a2d2728 EVP_MD_CTX_cleanup replaced with EVP_MD_CTX_reset
The EVP_MD_CTX_cleanup() function was merged into EVP_MD_CTX_reset()
which is called by EVP_MD_CTX_free().  Adjust the documentation to say
that the latter should be used to avoid leaking memory.

CLA: trivial

Reviewed-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5921)
2018-04-11 12:59:25 -04:00
.github
Configurations Fix minor typos in Configurations/README 2018-04-11 12:58:06 -04:00
VMS
apps apps/{s_client.c|s_socket}.c: omit usleep calls. 2018-04-08 11:42:35 +02:00
boringssl@2070f8ad91
crypto DRBG: fix memory leak on error in rand_drbg_get_entropy() 2018-04-10 10:33:17 +02:00
demos
doc EVP_MD_CTX_cleanup replaced with EVP_MD_CTX_reset 2018-04-11 12:59:25 -04:00
engines Update copyright year 2018-03-20 13:08:46 +00:00
external/perl
fuzz Update copyright year 2018-04-03 13:57:12 +01:00
include Support EVP_PKEY_sign() and EVP_PKEY_verify() for EdDSA 2018-04-06 10:10:05 +01:00
krb5@b9ad6c4950
ms Remove unused num.pl,segregnam scripts 2018-02-22 15:36:27 -05:00
os-dep
pyca-cryptography@c1f8e46033
ssl Move the loading of the ssl_conf module to libcrypto 2018-04-05 15:30:12 +01:00
test test/asn1_time_test.c: make it work on 64-bit HP-UX. 2018-04-08 11:17:44 +02:00
tools Update copyright year 2018-03-20 13:08:46 +00:00
util OpenSSL::Test: add data_dir() 2018-04-11 12:04:18 +02:00
.gitattributes
.gitignore Add test/versions to gitignore 2018-04-04 17:04:00 +01:00
.gitmodules
.travis-apt-pin.preferences
.travis-create-release.sh Reduce travis-ci log output 2018-03-08 21:18:35 +01:00
.travis.yml .travis.yml: with fast fuzz testing, there is no point avoiding it 2018-03-29 09:24:56 +02:00
ACKNOWLEDGEMENTS
AUTHORS
CHANGES Document the change in the previous commit about loading the config file 2018-04-05 15:30:12 +01:00
CONTRIBUTING Updated to CONTRIBUTING to reflect GitHub, etc. 2018-04-07 13:09:15 -04:00
Configure Fix minor typo in comment in Configure 2018-03-31 18:29:40 -04:00
FAQ
INSTALL Add documentation for the RAND_DRBG API 2018-03-30 00:10:38 +02:00
LICENSE Update the license end year 2018-01-20 10:02:23 +01:00
NEWS Update CHANGES and NEWS for the new release 2018-03-27 13:31:51 +01:00
NOTES.ANDROID Configurations/15-android.conf: detect clang by PATH, not by CC. 2018-03-19 14:31:30 +01:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX NOTES.UNIX: add additional note about --enable-new-dtags 2018-02-15 10:58:31 +01:00
NOTES.VMS
NOTES.WIN NOTES.WIN: classify targets to "native" and "hosted" and restructure. 2018-03-18 13:29:44 +01:00
README Prepare for 1.1.1-pre5-dev 2018-04-03 14:26:16 +01:00
README.ECC
README.ENGINE
README.FIPS
appveyor.yml appveyor.yml: omit makedepend step. 2018-02-24 14:17:24 +01:00
build.info VMS build.info: uppercase args to perl modules must be quoted 2017-12-18 07:49:53 +01:00
config config: fix hpux64-parisc2-gcc detection. 2018-04-08 11:18:22 +02:00
config.com Update copyright year 2018-02-13 13:59:25 +00:00
e_os.h Update copyright year 2018-02-27 13:59:42 +00:00

README

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