Go to file
Matt Caswell 4de88fe6da Implement a stricter ECX_KEY type
Add ref counting and control how we allocate storage for the private key.
We will need this type in following commits where we move the ecx code
to be provider aware.

Reviewed-by: Patrick Steuer <patrick.steuer@de.ibm.com>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/10964)
2020-02-11 22:32:47 +00:00
.github Add a GitHub issue template for documentation issues 2019-10-30 17:46:00 +01:00
apps Generalize the HTTP client so far implemented mostly in crypto/ocsp/ocsp_ht.c 2020-02-10 16:49:37 +01:00
boringssl@2070f8ad91
Configurations Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
crypto Implement a stricter ECX_KEY type 2020-02-11 22:32:47 +00:00
demos Remove RANDFILE settings from configuration files 2019-11-24 08:35:14 +01:00
doc Generalize the HTTP client so far implemented mostly in crypto/ocsp/ocsp_ht.c 2020-02-10 16:49:37 +01:00
engines Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
external/perl
fuzz Deprecate the ECDSA and EV_KEY_METHOD functions. 2020-02-04 20:02:55 +10:00
include Implement a stricter ECX_KEY type 2020-02-11 22:32:47 +00:00
krb5@890ca2f401 Update the krb5 submodule 2019-12-25 12:45:32 -08:00
ms
os-dep
providers PROV: Ensure the AlgorithmIdentifier registers in DSA signature impl 2020-02-10 10:22:32 +01:00
pyca-cryptography@09403100de
ssl Check that ed25519 and ed448 are allowed by the security level 2020-02-11 23:24:03 +01:00
test Implement a stricter ECX_KEY type 2020-02-11 22:32:47 +00:00
tools
util Generalize the HTTP client so far implemented mostly in crypto/ocsp/ocsp_ht.c 2020-02-10 16:49:37 +01:00
VMS
.gitattributes
.gitignore Add more generated man1 doc files 2020-01-29 18:42:30 +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 Add better support for using deprecated symbols internally 2019-12-13 10:09:49 +01:00
CHANGES Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
config config: ensure the perl Configure run is the last statement 2020-02-02 11:54:46 +01:00
config.com
configdata.pm.in configdata.pm.in: Don't try to quotify undefined values 2019-12-04 00:19:40 +01:00
Configure Configure: Add easy to use disabled deprecated functionality indicators 2020-02-07 14:54:36 +01:00
CONTRIBUTING Fix misspelling errors and typos reported by codespell 2020-02-06 17:01:00 +01:00
e_os.h Remove unused HAS_LFN_SUPPORT 2020-02-07 14:44:48 +10:00
FAQ
HACKING
INSTALL Deprecate most of debug-memory 2019-12-14 20:57:35 +01:00
LICENSE
NEWS Stop accepting certificates signed using SHA1 at security level 1 2020-02-05 22:04:37 +01:00
NOTES.ANDROID Remove spurious space from file. 2019-12-05 07:25:52 +10:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX
NOTES.VALGRIND
NOTES.VMS
NOTES.WIN
README Remove the version number in README 2019-10-18 12:22:00 +02:00
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.