Go to file
Rich Salz baf245ec5f GH528: "cipher -v" output is confusing.
Fix the docs, and refactor some common code.

Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
2016-01-11 18:54:49 -05:00
apps Use ossl_inline and DEFINE_LHASH_OF 2016-01-11 17:50:42 +00:00
certs
Configurations Enable/disable crypto-mdebug just like other features 2016-01-11 02:41:16 +00:00
crypto Function pop_info() returned a dangling pointer 2016-01-11 20:30:37 +01:00
demos mem functions cleanup 2016-01-07 15:14:18 -05:00
doc GH528: "cipher -v" output is confusing. 2016-01-11 18:54:49 -05:00
engines mem functions cleanup 2016-01-07 15:14:18 -05:00
include Use ossl_inline and DEFINE_LHASH_OF 2016-01-11 17:50:42 +00:00
ms
Netware
os2
ssl GH528: "cipher -v" output is confusing. 2016-01-11 18:54:49 -05:00
test Fix jpaketest compilation error. 2016-01-11 17:28:14 +00:00
tools
util Have mkdef.pl use case sensitive symbols for shareable symbol vector 2016-01-11 22:41:14 +01:00
VMS Remove the old VMS linker option file creator for shlibs 2016-01-07 21:09:43 +01:00
.gitignore Don't export internal symbols 2015-12-15 16:46:48 +00:00
.travis-create-release.sh Adapt the OS X build to use the OS X tar 2015-12-08 21:04:53 +01:00
.travis.yml Adapt the OS X build to use the OS X tar 2015-12-08 21:04:53 +01:00
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 2015-12-08 16:07:09 -05:00
appveyor.yml Add initial AppVeyor configuration 2015-11-21 18:06:31 +01:00
CHANGES GH528: "cipher -v" output is confusing. 2016-01-11 18:54:49 -05:00
config
Configure Adjust $default_depflags to changes in Configure 2016-01-11 11:06:28 +01:00
CONTRIBUTING
e_os.h Add ossl_inline 2015-12-22 23:03:56 +00:00
FAQ
GitConfigure
GitMake
INSTALL RT4202: Update rt URL's. 2015-12-28 16:40:40 -05:00
install.com
INSTALL.DJGPP
INSTALL.NW
INSTALL.OS2
INSTALL.VMS
INSTALL.W32
INSTALL.W64
INSTALL.WCE
LICENSE
Makefile.org Remove mkstack.pl: it is no longer needed. 2016-01-11 17:50:42 +00:00
Makefile.shared Don't export internal symbols 2015-12-15 16:46:48 +00:00
makevms.com
NEWS DANE CHANGES 2016-01-07 22:00:14 -05:00
openssl.doxy
openssl.spec
PROBLEMS
README RT4202: Update rt URL's. 2015-12-28 16:40:40 -05:00
README.ECC
README.ENGINE
README.FIPS Remove more (rest?) of FIPS build stuff. 2016-01-06 12:07:26 -05:00

 OpenSSL 1.1.0-pre2-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/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.