Go to file
Graeme Perrow 0704343f13 RT32671: wrong multiple errs TS_check_status_info
Reviewed-by: Tim Hudson <tjh@openssl.org>
Signed-off-by: Rich Salz <rsalz@openssl.org>
2015-11-13 16:36:43 -05:00
apps Continue standardisation of malloc handling in apps 2015-11-09 22:48:41 +00:00
certs
Configurations Configurations: move -Wno-pedantic-ms-format to .travis.yml. 2015-10-12 12:07:29 +02:00
crypto RT32671: wrong multiple errs TS_check_status_info 2015-11-13 16:36:43 -05:00
demos Replace "SSLeay" in API with OpenSSL 2015-10-30 17:21:42 -04:00
doc Fix SSL_use_certificate_chain_file 2015-11-10 23:02:44 +00:00
engines Continue malloc standardisation in engines 2015-11-09 22:48:41 +00:00
include Fix SSL_use_certificate_chain_file 2015-11-10 23:02:44 +00:00
ms
Netware
os2
ssl absent identity hint should be NULL 2015-11-13 16:00:29 +00:00
test Use uint32_t and int32_t for SSL_CIPHER structure. 2015-11-08 14:03:50 +00:00
tools Unwriteable directories are errors 2015-09-10 16:13:55 -04:00
util Fix SSL_use_certificate_chain_file 2015-11-10 23:02:44 +00:00
VMS
.gitignore Rationalize .gitignore and harmonize pair of Makefiles. 2015-09-29 18:02:35 +02:00
.travis.yml Run tests on Travis for mingw builds as well 2015-10-16 11:20:22 -04:00
ACKNOWLEDGEMENTS
CHANGES Replace "SSLeay" in API with OpenSSL 2015-10-30 17:21:42 -04:00
config
Configure Make the match for previous cflags a bit more strict 2015-11-09 09:50:56 +01:00
CONTRIBUTING Clarify the preferred way of creating patch files 2015-11-02 14:32:16 +00:00
e_os.h Replace "SSLeay" in API with OpenSSL 2015-10-30 17:21:42 -04:00
FAQ
GitConfigure
GitMake
INSTALL Extend the notes on how to do testing 2015-09-15 15:26:32 +02:00
install.com
INSTALL.DJGPP
INSTALL.NW
INSTALL.OS2
INSTALL.VMS Add a few notes on perl 2015-09-15 13:14:49 +02:00
INSTALL.W32
INSTALL.W64
INSTALL.WCE
LICENSE
Makefile.org Handle CT error macros separately 2015-10-21 23:57:29 +02:00
Makefile.shared
makevms.com RT3992: Make SCT #ifdeffable. 2015-09-09 18:28:13 -04:00
NEWS
openssl.doxy
openssl.spec
PROBLEMS Fixing typo in PROBLEMS 2015-09-27 20:50:40 -04:00
README Various README updates 2015-11-01 08:15:04 -05:00
README.ECC
README.ENGINE
README.FIPS

 OpenSSL 1.1.0-dev

 Copyright (c) 1998-2015 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 cryptograpic 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.a:
     Provides the client and server-side implementations for SSLv3 and TLS.

 libcrypto.a:
     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, etc.
        INSTALL.DJGPP   DOS platform with DJGPP
        INSTALL.NW      Netware
        INSTALL.OS2     OS/2
        INSTALL.VMS     VMS
        INSTALL.W32     Windows (32bit)
        INSTALL.W64     Windows (64bit)
        INSTALL.WCE     Windows CE

 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/support/rt.html 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.