Go to file
Rob Percival 505fb99964 Change CA.pl flag from --newprecert to --precert
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/843)
2017-02-22 10:40:30 -05:00
.github Don't need the checkbox; the hook does it 2017-01-28 17:26:56 -05:00
apps Change CA.pl flag from --newprecert to --precert 2017-02-22 10:40:30 -05:00
boringssl@490469f850 Run BoringSSL tests on Travis 2016-11-24 12:21:33 +01:00
Configurations appveyor.yml: engage VC-WIN64A-masm. 2017-02-21 22:39:00 +01:00
crypto Fix memory leak in pkcs12 -export 2017-02-21 14:47:18 -05:00
demos Crude VMS build files for demos/bio/ 2016-09-20 18:24:24 +02:00
doc Documentation for the -precert flag for "openssl req" 2017-02-22 10:40:30 -05:00
engines e_afalg: Don't warn about kernel version when pedantic 2016-12-16 14:43:49 +01:00
external/perl
fuzz Update client, server and x509 fuzz corpus 2017-02-21 18:53:07 +01:00
include Implementation of the ARIA cipher as described in RFC 5794. 2017-02-21 11:51:45 +01:00
ms
os-dep
ssl Add some more consistency checks in tls_decrypt_ticket. 2017-02-22 09:36:02 -05:00
test Change CA.pl flag from --newprecert to --precert 2017-02-22 10:40:30 -05:00
tools Add -h and -help for c_rehash script and app 2016-09-14 08:59:48 -04:00
util Implementation of the ARIA cipher as described in RFC 5794. 2017-02-21 11:51:45 +01:00
VMS VMS: Don't force symbol mixed case when building DSOs 2016-09-11 23:18:03 +02:00
.gitattributes crypto/pkcs12: facilitate accessing data with non-interoperable password. 2016-08-22 13:52:59 +02:00
.gitignore Review comments; fail build if nits found 2017-01-12 09:31:36 -05:00
.gitmodules Run BoringSSL tests on Travis 2016-11-24 12:21:33 +01:00
.travis-create-release.sh
.travis.yml .travis.yml: remove osx from build matrix. 2017-02-19 21:27:57 +01:00
ACKNOWLEDGEMENTS
appveyor.yml appveyor.yml: engage VC-WIN64A-masm. 2017-02-21 22:39:00 +01:00
AUTHORS
build.info
CHANGES Update CHANGES and NEWS for new release 2017-02-16 10:10:05 +00:00
config Implementation of the ARIA cipher as described in RFC 5794. 2017-02-21 11:51:45 +01:00
config.com VMS: no ENDIF on one line IF statements, in config.com 2016-08-17 10:48:43 +02:00
Configure Implementation of the ARIA cipher as described in RFC 5794. 2017-02-21 11:51:45 +01:00
CONTRIBUTING Update the location of the pod files 2016-11-18 07:28:03 -05:00
e_os.h Revert "Use memcmp() instead of CRYPTO_memcmp() when fuzzing" 2017-02-20 18:54:39 +01:00
FAQ
INSTALL Add support for parameterized SipHash 2017-02-01 14:14:36 -05:00
LICENSE
Makefile.shared HPUX: Add the forgotten $(DSTDIR) when linking DSOs 2016-11-01 00:51:03 +01:00
NEWS Update CHANGES and NEWS for new release 2017-02-16 10:10:05 +00:00
NOTES.DJGPP
NOTES.PERL
NOTES.VMS Add a note about a perl issue on VMS and how to work around it 2016-08-06 16:00:13 +02:00
NOTES.WIN Fix typo 2016-10-14 10:01:54 +01:00
README Fix typo (reported by Matthias St. Pierre) 2016-10-26 11:48:43 -04:00
README.ECC
README.ENGINE
README.FIPS

 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.