Go to file
Andy Polyakov 90edbfcce3 include/openssl/e_os2.h: fix 'noreturn' pre-processor logic.
Newer gcc still recognizes e.g. -std=c9x in which case it wouldn't
have used 'noreturn' at all with original logic.

Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-05-27 23:05:03 +02:00
apps Fix intermittent windows failures in TLSProxy tests 2016-05-27 15:18:54 +01:00
Configurations Windows makefile: handle the case with space in source directory 2016-05-27 17:41:32 +02:00
crypto crypto/o_str.c: add _GNU_SOURCE strerror_r case. 2016-05-27 23:02:56 +02:00
demos
doc Update the documentation of BN_hex2bn() 2016-05-27 10:05:44 +01:00
engines build.info files: add quotes around any spec that may contain spaces 2016-05-25 11:50:44 +02:00
external/perl
fuzz
include include/openssl/e_os2.h: fix 'noreturn' pre-processor logic. 2016-05-27 23:05:03 +02:00
ms
os-dep
ssl Fix ssl_cert_set0_chain invalid pointer 2016-05-27 17:20:10 +01:00
test make sure to put quotes around -config argument, in case of spaces 2016-05-27 17:41:32 +02:00
tools Make sure tsget and c_rehash are named with .pl suffix on Windows and VMS 2016-05-23 21:48:42 +02:00
util perl glob: make sure to put quotes around the pattern, in case of spaces 2016-05-27 17:41:32 +02:00
VMS Make sure tsget.pl and c_rehash.pl get installed on VMS and Windows. 2016-05-23 21:48:42 +02:00
.gitattributes
.gitignore Add text/x509aux to gitignore 2016-05-23 13:55:16 +01:00
.travis-create-release.sh
.travis.yml
ACKNOWLEDGEMENTS
appveyor.yml
AUTHORS
build.info build.info files: add quotes around any spec that may contain spaces 2016-05-25 11:50:44 +02:00
CHANGES
config
config.com
Configure Configure: handle spaces in source directory spec 2016-05-27 17:41:32 +02:00
CONTRIBUTING
e_os.h Handle Visual C warning about non-standard function names. 2016-05-26 00:48:23 +02:00
FAQ
INSTALL Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
LICENSE
Makefile.shared Makefile.shared: revert Haiku support commit. 2016-05-25 23:47:55 +02:00
NEWS
NOTES.DJGPP Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
NOTES.PERL Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
NOTES.VMS
NOTES.WIN Windows notes: add a few lines on gaining admin privs for installing 2016-05-23 22:24:13 +02:00
README Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
README.ECC
README.ENGINE
README.FIPS

 OpenSSL 1.1.0-pre6-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
 Secure Sockets Layer (SSLv3) and Transport Layer Security (TLS) protocols as
 well as a full-strength general purpose cryptographic library. The project is
 managed by a worldwide community of volunteers that use the Internet to
 communicate, plan, and develop the OpenSSL toolkit and its related
 documentation.

 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.

 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:

    - On Unix systems:
        Self-test report generated by 'make report'
    - On other systems:
        OpenSSL version: output of 'openssl version -a'
        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 day for the ticket to show up.  (We also scan posts to make sure
 that security disclosures aren't publically 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.

 You can also make GitHub pull requests. If you do this, please also send
 mail to rt@openssl.org with a link to the PR so that we can more easily
 keep track of it.

 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.