Go to file
Richard Levitte b23238f9aa Keep a cache of files that already have a recipe, in common.tmpl
We don't want recipes for the same files generated more than once

Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-02-27 19:17:45 +01:00
apps Drop support for printing SSLv2 ciphers names. 2016-02-27 13:07:10 +01:00
certs
Configurations Keep a cache of files that already have a recipe, in common.tmpl 2016-02-27 19:17:45 +01:00
crypto GH753: More spelling fix 2016-02-27 10:58:16 -05:00
demos Finish 02f7114a7f 2016-02-17 17:04:47 -05:00
doc GH753: More spelling fix 2016-02-27 10:58:16 -05:00
engines Remove Ubsec engine 2016-02-26 23:34:25 +00:00
external/perl Adjust transfer::Text::Template.pm for alternate directory name 2016-02-12 18:04:49 +01:00
include GH753: More spelling fix 2016-02-27 10:58:16 -05:00
ms
Netware
os2
ssl GH715: ENGINE_finish can take NULL 2016-02-25 15:19:42 -05:00
test testutil.c includes e_os.h. 2016-02-27 16:22:38 +00:00
tools Rename INSTALL_PREFIX to DESTDIR, remove option --install_prefix 2016-02-12 21:54:07 +01:00
util Public API for Certificate Transparency 2016-02-26 14:57:29 -05:00
VMS Clean away $config{no_shared} since we have $disabled{shared} 2016-02-22 16:36:58 +01:00
.gitignore Update .gitignore. 2016-02-12 21:49:34 +01:00
.travis-create-release.sh
.travis.yml Don't build sanitizer builds with --debug 2016-02-26 18:35:08 +01:00
ACKNOWLEDGEMENTS
appveyor.yml
build.info Big rename fest of MingW shared libraries 2016-02-19 11:52:16 +01:00
CHANGES GH753: More spelling fix 2016-02-27 10:58:16 -05:00
config Remove all -march= from configs 2016-02-23 00:47:52 +01:00
config.com Lowercase configuration arguments on VMS 2016-02-16 16:10:06 +01:00
Configure Apply default after having checked the given config target is valid 2016-02-27 14:27:25 +01:00
CONTRIBUTING
e_os.h Remove unused parameters from internal functions 2016-02-22 13:39:44 -05:00
FAQ
GitConfigure
GitMake
INSTALL Rename INSTALL_PREFIX to DESTDIR, remove option --install_prefix 2016-02-12 21:54:07 +01:00
INSTALL.DJGPP
INSTALL.NW
INSTALL.OS2
INSTALL.VMS
INSTALL.WCE
INSTALL.WIN
LICENSE
Makefile.in Public API for Certificate Transparency 2016-02-26 14:57:29 -05:00
Makefile.shared FreeBSD, at least, can restrict symbols in a shared library - so use the 2016-02-27 16:23:25 +00:00
NEWS
openssl.doxy
openssl.spec Rename INSTALL_PREFIX to DESTDIR, remove option --install_prefix 2016-02-12 21:54:07 +01:00
PROBLEMS
README Prepare for 1.1.0-pre4-dev 2016-02-15 19:37:42 +01:00
README.ECC
README.ENGINE Remove Ubsec engine 2016-02-26 23:34:25 +00:00
README.FIPS
README.PERL

 OpenSSL 1.1.0-pre4-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.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.WIN     Windows
        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.