TLS/SSL and crypto library
Find a file
Richard Levitte 7638370ca6 Make the definition of EVP_MD_CTX opaque
This moves the definitionto crypto/evp/evp_locl.h, along with a few
associated accessor macros.  A few accessor/writer functions added.

Reviewed-by: Rich Salz <rsalz@openssl.org>
2015-12-07 17:36:57 +01:00
apps Remove support for all 40 and 56 bit ciphers. 2015-12-05 17:45:59 +01:00
certs grammar 2008-05-27 18:43:20 +00:00
Configurations Configuratons: add -DFILIO_H to harmonized Solaris targets. 2015-11-24 23:06:13 +01:00
crypto Make the definition of EVP_MD_CTX opaque 2015-12-07 17:36:57 +01:00
demos Remove support for all 40 and 56 bit ciphers. 2015-12-05 17:45:59 +01:00
doc Fix typo and improve a bit of text 2015-12-06 22:22:44 -05:00
engines Remove RSA_FLAG_SIGN_VER flag. 2015-12-02 18:23:29 +00:00
include Make the definition of EVP_MD_CTX opaque 2015-12-07 17:36:57 +01:00
ms Fix various windows compilation issues 2015-01-28 22:55:15 +00:00
Netware Remove SSLv2 support 2014-12-04 11:55:03 +01:00
os2 Make a number of changes to the OS/2 build. Submitter's comment below. 2003-11-28 14:51:30 +00:00
ssl Really disable 56-bit (single-DES) ciphers 2015-12-06 12:32:19 -05:00
test Remove support for all 40 and 56 bit ciphers. 2015-12-05 17:45:59 +01:00
tools Unwriteable directories are errors 2015-09-10 16:13:55 -04:00
util Remove support for all 40 and 56 bit ciphers. 2015-12-05 17:45:59 +01:00
VMS Teach mkshared.com to have a look for disabled algorithms in opensslconf.h 2011-10-30 11:40:54 +00:00
.gitignore Rationalize .gitignore and harmonize pair of Makefiles. 2015-09-29 18:02:35 +02:00
.travis.yml In travis, build from a "source release" rather than from the build tree 2015-12-07 16:12:22 +01:00
ACKNOWLEDGEMENTS Cleanup some doc files 2015-03-01 20:46:38 -05:00
appveyor.yml Add initial AppVeyor configuration 2015-11-21 18:06:31 +01:00
CHANGES Fix and update versions in CHANGES and NEWS 2015-12-07 14:30:30 +00:00
config Remove remaining Kerberos references 2015-05-13 15:08:10 +01:00
Configure Fix ./Configure reconf 2015-12-02 19:39:36 +01:00
CONTRIBUTING Clarify the preferred way of creating patch files 2015-11-02 14:32:16 +00:00
e_os.h Configuratons: add -DFILIO_H to harmonized Solaris targets. 2015-11-24 23:06:13 +01:00
FAQ Move FAQ to the web. 2015-08-16 19:02:29 -04:00
GitConfigure Remove remaining variables for symlinked/copied headers and tests 2015-03-31 20:16:01 +02:00
GitMake Build on MacOS. 2014-02-09 12:49:04 +00:00
INSTALL Extend the notes on how to do testing 2015-09-15 15:26:32 +02:00
install.com After some adjustments, apply the changes OpenSSL 1.0.0d on OpenVMS 2011-03-19 10:58:14 +00:00
INSTALL.DJGPP INSTALL.DJGPP sync. 2005-01-14 16:25:36 +00:00
INSTALL.NW misspellings fixes by https://github.com/vlajos/misspell_fixer 2013-09-05 21:39:42 +01:00
INSTALL.OS2 Add support for shared libraries with OS/2. 2002-07-17 13:27:43 +00:00
INSTALL.VMS Add a few notes on perl 2015-09-15 13:14:49 +02:00
INSTALL.W32 FAQ/README: we are now using Git instead of CVS 2013-02-11 11:33:29 +01:00
INSTALL.W64 Pull up Win64 support from 0.9.8. 2005-07-05 11:44:45 +00:00
INSTALL.WCE First draft for WCE PortSDK support. Once again! It's *draft* which requires 2005-11-06 20:52:26 +00:00
LICENSE OCSP stapling fix (OpenSSL 0.9.8r/1.0.0d) 2011-02-08 17:48:57 +00:00
Makefile.org Do not add symlinks in the source release 2015-12-07 16:12:22 +01:00
Makefile.shared RT3548: Remove some unsupported platforms. 2015-01-12 10:40:00 -05:00
makevms.com RT3992: Make SCT #ifdeffable. 2015-09-09 18:28:13 -04:00
NEWS Fix and update versions in CHANGES and NEWS 2015-12-07 14:30:30 +00:00
openssl.doxy Add functions to add certs to stacks, used for CA file/path stuff in servers. 1999-02-28 17:41:55 +00:00
openssl.spec Simplify and update openssl.spec 2013-11-30 14:11:05 +00:00
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 Add NSA sublicense info. 2011-05-11 12:50:57 +00:00
README.ENGINE oops, there were other cases of "ENGINE_ID" to change too. 2002-07-08 15:16:10 +00:00
README.FIPS Build fipscanister.o only by default. Utility build now needs 2011-10-19 11:47:21 +00:00

 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.