node/deps/openssl/openssl
Evan Lucas d06ff289a0 deps: add openssl support for arm64
This adds the required files for supporting openssl
on arm64.

This uses the same configuration that can be found in
https://github.com/openssl/openssl/pull/12369 to generate the required
files.

PR-URL: https://github.com/nodejs/node/pull/34238
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ash Cripps <ashley.cripps@ibm.com>
2020-08-25 10:54:43 -05:00
..
Configurations deps: add openssl support for arm64 2020-08-25 10:54:43 -05:00
VMS deps: upgrade openssl sources to 1.1.1a 2019-01-22 13:32:34 -08:00
apps deps: upgrade openssl sources to 1.1.1g 2020-04-27 07:29:48 -07:00
crypto deps: add support for BoringSSL QUIC APIs 2020-06-16 09:22:39 -07:00
demos deps: upgrade openssl sources to 1.1.1d 2019-10-01 11:07:43 -07:00
doc deps: cherry-pick akamai/openssl/commit/a6282c566d88db11300c82abc3c84a4e2e9ea568 2020-06-24 12:32:56 -07:00
engines deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
external/perl deps: upgrade openssl sources to 1.1.0i 2018-08-16 11:52:37 +10:00
fuzz deps: upgrade openssl sources to 1.1.1c 2019-06-17 11:55:44 +02:00
include deps: cherry-pick akamai/openssl/commit/a6282c566d88db11300c82abc3c84a4e2e9ea568 2020-06-24 12:32:56 -07:00
ms deps: upgrade openssl sources to 1.1.1b 2019-03-05 08:34:43 -08:00
os-dep deps: upgrade openssl sources to 1.1.0h 2018-04-10 06:45:42 +09:00
ssl deps: re-enable OPENSSL_NO_QUIC guards 2020-06-24 12:33:22 -07:00
test deps: cherry-pick akamai/openssl/commit/a5a08cb8050bb69120e833456e355f482e392456 2020-06-24 12:33:03 -07:00
tools deps: upgrade openssl sources to 1.1.1a 2019-01-22 13:32:34 -08:00
util deps: cherry-pick akamai/openssl/commit/a6282c566d88db11300c82abc3c84a4e2e9ea568 2020-06-24 12:32:56 -07:00
ACKNOWLEDGEMENTS deps: upgrade openssl sources to 1.1.0h 2018-04-10 06:45:42 +09:00
AUTHORS deps: upgrade openssl sources to 1.1.1a 2019-01-22 13:32:34 -08:00
CHANGES deps: add support for BoringSSL QUIC APIs 2020-06-16 09:22:39 -07:00
CONTRIBUTING deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
Configure deps: add support for BoringSSL QUIC APIs 2020-06-16 09:22:39 -07:00
FAQ deps: upgrade openssl sources to 1.0.2e 2015-12-04 03:56:12 +09:00
INSTALL deps: add support for BoringSSL QUIC APIs 2020-06-16 09:22:39 -07:00
LICENSE deps: upgrade openssl sources to 1.1.1b 2019-03-05 08:34:43 -08:00
NEWS deps: upgrade openssl sources to 1.1.1g 2020-04-27 07:29:48 -07:00
NOTES.ANDROID deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
NOTES.DJGPP deps: upgrade openssl sources to 1.1.1b 2019-03-05 08:34:43 -08:00
NOTES.PERL deps: upgrade openssl sources to 1.1.1c 2019-06-17 11:55:44 +02:00
NOTES.UNIX deps: upgrade openssl sources to 1.1.1a 2019-01-22 13:32:34 -08:00
NOTES.VMS deps: upgrade openssl sources to 1.1.1b 2019-03-05 08:34:43 -08:00
NOTES.WIN deps: upgrade openssl sources to 1.1.1d 2019-10-01 11:07:43 -07:00
README deps: upgrade openssl sources to 1.1.1g 2020-04-27 07:29:48 -07:00
README.ENGINE deps: upgrade openssl sources to 1.1.1a 2019-01-22 13:32:34 -08:00
README.FIPS deps: upgrade openssl sources to 1.1.0h 2018-04-10 06:45:42 +09:00
appveyor.yml deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
build.info deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
config deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00
config.com deps: upgrade openssl sources to 1.1.0h 2018-04-10 06:45:42 +09:00
e_os.h deps: upgrade openssl sources to 1.1.1e 2020-03-23 07:37:11 -07:00

README

 OpenSSL 1.1.1g 21 Apr 2020

 Copyright (c) 1998-2020 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.