TLS/SSL and crypto library
Find a file
Dr. Stephen Henson 24762dee17 Update S/MIME certificates.
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
2016-05-11 18:00:52 +01:00
apps Fix NULL deref in apps/pkcs7 2016-04-25 11:46:52 -04:00
bugs Run util/openssl-format-source -v -c . 2015-01-22 09:38:39 +00:00
certs grammar 2008-05-27 18:43:20 +00:00
crypto Only call FIPS_update, FIPS_final in FIPS mode. 2016-05-09 02:10:28 +01:00
demos Fix more URLs mangled by reformat 2015-12-19 20:40:39 +00:00
doc add documentation 2016-05-04 13:00:17 +01:00
engines Remove the "eay" c-file-style indicators 2015-12-18 13:13:31 +01:00
MacOS Run util/openssl-format-source -v -c . 2015-01-22 09:38:39 +00:00
ms ms/uplink-x86.pl: make it work. 2016-02-10 12:57:29 +01:00
Netware Update netware to use new SHA2 assembly language modules. 2008-01-04 13:18:09 +00:00
os2 Make a number of changes to the OS/2 build. Submitter's comment below. 2003-11-28 14:51:30 +00:00
shlib Apply mingw patches as supplied by Roumen Petrov an Alon Bar-Lev 2008-04-17 10:19:16 +00:00
ssl Fix memory leak on invalid CertificateRequest. 2016-04-07 19:27:45 +01:00
test Update S/MIME certificates. 2016-05-11 18:00:52 +01:00
times PR: 1894 2009-04-16 17:22:51 +00:00
tools RT4044: Remove .cvsignore files. 2015-09-15 12:00:18 -04:00
util Fix the no-comp option for Windows 2016-03-18 12:17:06 +00:00
VMS Teach mkshared.com to have a look for disabled algorithms in opensslconf.h 2011-10-30 11:40:56 +00:00
.gitignore Ignore .dir-locals.el 2015-09-01 01:19:52 +02:00
.travis-create-release.sh Adapt the OS X build to use the OS X tar 2015-12-08 21:06:34 +01:00
.travis.yml Adapt the OS X build to use the OS X tar 2015-12-08 21:06:34 +01:00
ACKNOWLEDGMENTS Refer to website for acknowledgements. 2015-12-08 16:08:20 -05:00
appveyor.yml Add initial AppVeyor configuration 2015-11-21 20:15:54 +01:00
CHANGES Prepare for 1.0.1u-dev 2016-05-03 14:50:37 +01:00
CHANGES.SSLeay PR: 1894 2009-04-16 17:22:51 +00:00
config config: fix executable format detection on latest FreeBSD. 2013-07-01 00:00:20 +02:00
Configure Disable EXPORT and LOW SSLv3+ ciphers by default 2016-03-01 11:24:02 +00:00
CONTRIBUTING Clarify the preferred way of creating patch files 2015-11-02 14:34:40 +00:00
e_os.h e_os.h: limit _MSC_VER trickery to older compilers. 2015-12-03 13:24:42 +01:00
e_os2.h Add the macro OPENSSL_SYS_WIN64 2015-06-02 18:05:31 +02:00
FAQ Move FAQ to the web. 2015-08-16 19:04:03 -04:00
INSTALL RT4202: Update rt URL's. 2015-12-28 16:41:28 -05:00
install.com Apply all the changes submitted by Steven M. Schweda <sms@antinode.info> 2011-03-19 09:47:47 +00:00
INSTALL.DJGPP INSTALL.DJGPP sync. 2005-01-14 16:25:36 +00:00
INSTALL.MacOS Typos (Chris Pepper <pepper@mail.reppep.com>) 2001-10-01 14:43:47 +00:00
INSTALL.NW Netware support. 2008-01-03 22:43:04 +00:00
INSTALL.OS2 Add support for shared libraries with OS/2. 2002-07-17 13:27:43 +00:00
INSTALL.VMS Change INSTALL.VMS to reflect the changes done on the build and 2011-03-19 09:48:15 +00:00
INSTALL.W32 FAQ/README: we are now using Git instead of CVS 2013-02-11 11:29:05 +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 Update license year range to 2016 2016-01-19 10:24:52 -05:00
Makefile.org TARFILE wasn't correctly set 2016-01-28 17:06:38 +00:00
Makefile.shared Makefile.shared: fix brown-bag typo in link_o.darwin [from HEAD]. 2010-08-21 11:37:17 +00:00
makevms.com Define CFLAGS as cflags on VMS as well 2015-01-14 00:16:21 +01:00
NEWS Prepare for 1.0.1u-dev 2016-05-03 14:50:37 +01: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 Prepare for 1.0.1u-dev 2016-05-03 14:50:37 +01:00
PROBLEMS ./Configure: libcrypto.a can grow to many GB on Solaris 10, because of ar bug 2012-08-13 16:18:59 +00:00
README Prepare for 1.0.1u-dev 2016-05-03 14:50:37 +01:00
README.ASN1 Merge from the ASN1 branch of new ASN1 code 2000-12-08 19:09:35 +00:00
README.ENGINE oops, there were other cases of "ENGINE_ID" to change too. 2002-07-08 15:16:10 +00:00
TABLE Housekeeping 'make TABLE' update. 2015-05-26 21:55:57 +02:00

 OpenSSL 1.0.1u-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.