TLS/SSL and crypto library
Find a file
Matt Caswell eaa32f3679 Fix no-ec and no-tls1_2
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/7620)

(cherry picked from commit 65d2c16cbe)
2018-11-14 11:33:24 +00:00
.github
apps Added missing signature algorithm reflection functions 2018-11-12 16:53:32 -05:00
boringssl@2070f8ad91
Configurations test/recipes/90-test_shlibload.t needs $target{shared_extension} 2018-11-14 00:42:58 +01:00
crypto Fix SipHash init order. 2018-11-12 07:16:58 +01:00
demos demos/evp: add make clean 2018-09-04 08:07:22 +10:00
doc Added missing signature algorithm reflection functions 2018-11-12 16:53:32 -05:00
engines Update copyright year 2018-09-11 13:45:17 +01:00
external/perl Update copyright year 2018-09-11 13:45:17 +01:00
fuzz print() is a function in Python 3 2018-10-17 07:32:25 +02:00
include Added missing signature algorithm reflection functions 2018-11-12 16:53:32 -05:00
krb5@b9ad6c4950
ms Update copyright year 2018-05-01 13:34:30 +01:00
os-dep
pyca-cryptography@09403100de Update the pyca-cryptography submodule 2018-09-10 12:04:03 +01:00
ssl Fix no-ec and no-tls1_2 2018-11-14 11:33:24 +00:00
test Fix no-ec and no-tls1_2 2018-11-14 11:33:24 +00:00
tools Update copyright year 2018-03-20 13:08:46 +00:00
util Fix typo in util/perl/OpenSSL/Test.pm 2018-11-14 00:54:29 +01:00
VMS
.gitattributes
.gitignore Add a compile time test to verify that openssl/rsa.h and complex.h can 2018-09-17 09:44:45 +10: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 Revert ".travis.yml: omit linux-ppc64le target." 2018-08-31 10:56:35 +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 Update AUTHORS list, add commentary 2018-07-08 20:32:04 -04:00
build.info Configurations/10-main.conf: replace -bexpall with explicit list on AIX. 2018-06-13 10:48:27 +02:00
CHANGES EVP module documentation pass 2018-10-17 13:31:59 +03:00
config Configure: move --noexecstack probe to Configure. 2018-05-05 20:44:56 +02:00
config.com Update copyright year 2018-02-13 13:59:25 +00:00
Configure Configuration: make sure the shared_sources table doesn't contain empty elements 2018-11-13 18:49:37 +01:00
CONTRIBUTING Add a note on CHANGES and NEWS in CONTRIBUTING 2018-05-17 13:51:11 +02:00
e_os.h test/secmemtest: test secure memory only if it is implemented 2018-10-05 12:23:34 +02:00
FAQ
INSTALL typo-fixes: miscellaneous typo fixes 2018-09-21 23:59:02 +02:00
LICENSE Update the license end year 2018-01-20 10:02:23 +01:00
NEWS Prepare for 1.1.1a-dev 2018-09-11 13:49:46 +01:00
NOTES.ANDROID Configurations/15-android.conf: add support for "standalone toolchain". 2018-10-19 10:36:48 +02:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX NOTES.UNIX: add "Linking your application" paragraph 2018-06-26 12:28:06 +02:00
NOTES.VMS
NOTES.WIN INSTALL,NOTES.WIN: classify no-asm as non-production option. 2018-07-25 15:47:12 +02:00
README Prepare for 1.1.1a-dev 2018-09-11 13:49:46 +01:00
README.ENGINE
README.FIPS

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