Go to file
Richard Levitte 5cdad22f3e Move the building of test/buildtest_*. to be done unconditionally
These were guarded by $disabled{tests}.  However, 'tests' is disabled
if we configure 'no-stdio', which means that we don't detect the lack
of OPENSSL_NO_STDIO guards in our public header files.  So we move the
generation and build of test/buildtest_*.c to be unconditional.

Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-08-05 21:17:05 +02:00
apps Make update, etc. 2016-08-05 11:19:33 -04:00
Configurations When tr gets bracketed arguments, they need to be quoted 2016-08-04 21:02:37 +02:00
crypto Sanity check input length in OPENSSL_uni2asc(). 2016-08-05 18:58:56 +01:00
demos
doc Constify some ASN1_OBJECT *obj input parameters 2016-08-04 17:02:48 +02:00
engines Use _NO_INST in some build.info files 2016-07-18 20:49:54 +02:00
external/perl
fuzz Some minor tweaks to the fuzzing docs 2016-08-01 22:07:04 +01:00
include Added appropriate OPENSSL_NO_STDIO to PKCS12 header 2016-08-05 02:00:39 +02:00
ms
os-dep
ssl Fix ubsan 'left shift of negative value -1' error in satsub64be() 2016-08-04 20:56:24 +01:00
test Move the building of test/buildtest_*. to be done unconditionally 2016-08-05 21:17:05 +02:00
tools perl: Separate compile-time environment from runtime environment 2016-07-04 15:40:31 +02:00
util Make update, etc. 2016-08-05 11:19:33 -04:00
VMS VMS: have the IVP verify that a well known engine loads properly 2016-08-04 16:57:49 +02:00
.gitattributes
.gitignore Ignore windows generated manifests 2016-08-04 17:05:48 +02:00
.travis-create-release.sh
.travis.yml Add --gcov-options '\-lp' to coverage 2016-08-05 18:01:39 +02:00
ACKNOWLEDGEMENTS
appveyor.yml
AUTHORS
build.info Have the VMS shared library file names contain the shared version 2016-07-02 15:49:45 +02:00
CHANGES Fix date in CHANGES 2016-08-04 14:55:41 +01:00
config
config.com VMS: arch in config.com was mistakenly made process global 2016-07-06 01:23:41 +02:00
Configure Add memory sanitizer config, and run on travis. 2016-07-28 21:43:27 +02:00
CONTRIBUTING
e_os.h
FAQ
INSTALL INSTALL: Make the use of [, ], { and } consistent and explain it 2016-08-03 15:46:52 +02:00
LICENSE
Makefile.shared
NEWS
NOTES.DJGPP
NOTES.PERL
NOTES.VMS
NOTES.WIN
README Prepare for 1.1.0-pre7-dev 2016-08-04 15:02:43 +01:00
README.ECC
README.ENGINE
README.FIPS

 OpenSSL 1.1.0-pre7-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 current snapshot from ftp://ftp.openssl.org/snapshot/
      to see if the problem has already been addressed
    - Remove ASM versions of libraries
    - Remove compiler optimisation flags

 If you wish to report a bug then please include the following information in
 any bug report:

    - 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)

 Email the report to:

    rt@openssl.org

 In order to avoid spam, this is a moderated mailing list, and it might
 take a couple of days for the ticket to show up.  (We also scan posts to make
 sure that security disclosures aren't publicly posted by mistake.) Mail
 to this address is recorded in the public RT (request tracker) database
 (see https://www.openssl.org/community/index.html#bugs for details) and
 also forwarded the public openssl-dev mailing list.  Confidential mail
 may be sent to openssl-security@openssl.org (PGP key available from the
 key servers).

 Please do NOT use this for general assistance or support queries.
 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.

 You can also make GitHub pull requests. See the CONTRIBUTING file for more
 details.

 HOW TO CONTRIBUTE TO OpenSSL
 ----------------------------

 See CONTRIBUTING

 LEGALITIES
 ----------

 A number of nations, in particular the U.S., 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.