Go to file
Richard Levitte 619eb33a0c Add new /dev/crypto engine
Based on cryptodev-linux

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/3744)
2017-06-28 12:54:33 +02:00
.github Remind people to have 'Fixes #XXXX' in the commit message 2017-04-02 21:51:47 +02:00
Configurations Add new /dev/crypto engine 2017-06-28 12:54:33 +02:00
VMS
apps Use randomness not entropy 2017-06-27 12:14:49 -04:00
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 2017-03-14 12:12:13 +00:00
crypto Add new /dev/crypto engine 2017-06-28 12:54:33 +02:00
demos Fix a bundle of trailing spaces in several files 2017-06-09 12:04:10 -04:00
doc Use randomness not entropy 2017-06-27 12:14:49 -04:00
engines Put message strings in state files 2017-06-12 15:03:40 -04:00
external/perl
fuzz fuzz/{client,server}.c: omit _time64 "overload method". 2017-04-27 13:01:08 +02:00
include Add new /dev/crypto engine 2017-06-28 12:54:33 +02:00
krb5@b9ad6c4950 [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
ms Remove filename argument to x86 asm_init. 2017-05-11 17:00:23 -04:00
os-dep
pyca-cryptography@139b25f2ba Update the pyca-cryptography version 2017-05-26 18:00:33 +01:00
ssl Disallow DSA/SHA1/etc. for pure TLS 1.3 ClientHellos 2017-06-24 19:25:43 -05:00
test Use randomness not entropy 2017-06-27 12:14:49 -04:00
tools
util util/mkerr.pl: avoid getting an annoying warning about negative count 2017-06-27 14:49:06 +02:00
.gitattributes
.gitignore Add apps/progs.h to gitignore 2017-06-15 16:56:56 -04: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 Fix travis clang-3.9 builds 2017-06-23 17:57:02 +01:00
ACKNOWLEDGEMENTS
AUTHORS
CHANGES util/mkerr.pl: allow module names prefixed with OSSL_ or OPENSSL_ 2017-06-27 14:49:06 +02:00
CONTRIBUTING Update the location of the pod files 2016-11-18 07:28:03 -05:00
Configure Add new /dev/crypto engine 2017-06-28 12:54:33 +02:00
FAQ
INSTALL drop some no-longer-relevant TODO(TLS1.3) entries 2017-06-12 09:19:05 +01:00
LICENSE Update year, wording tweak 2017-02-28 10:13:32 -05:00
Makefile.shared Code health: Remove base address setting for mingw 2017-02-28 21:31:32 +01:00
NEWS util/mkerr.pl: allow module names prefixed with OSSL_ or OPENSSL_ 2017-06-27 14:49:06 +02:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX Add NOTES.UNIX, with a description on how to deal with runpaths 2017-03-02 07:33:27 +01:00
NOTES.VMS More typo fixes 2017-03-29 07:14:29 +02:00
NOTES.WIN NOTES.WIN: mention Strawberry Perl as option. 2017-03-15 12:17:52 +01:00
README Fix typo (reported by Matthias St. Pierre) 2016-10-26 11:48:43 -04: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
config Better way to recognise mingw64 in config script 2017-03-13 21:41:20 +01:00
config.com
e_os.h Use randomness not entropy 2017-06-27 12:14:49 -04: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 optimisation 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.