A local copy of OpenSSL from GitHub
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Lutz Jaenicke 9fa24352ce FAQ/README: we are now using Git instead of CVS
(cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af)
10 years ago
Netware Update netware to use new SHA2 assembly language modules. 16 years ago
VMS Teach mkshared.com to have a look for disabled algorithms in opensslconf.h 12 years ago
apps Improve WINCE support. 11 years ago
bugs Keep disclaming 16-bit support. 18 years ago
certs grammar 15 years ago
crypto sparccpuid.S: work around emulator bug on T1. 10 years ago
demos oops, revert, committed in error 11 years ago
doc Correct EVP_PKEY_verifyrecover to EVP_PKEY_verify_recover (RT 2955). 11 years ago
engines Don't use C++ style comments. 11 years ago
fips fips/fipsld: improve cross-compile support. 11 years ago
include Add emacs cache files to .cvsignore. 18 years ago
ms x86_64 assembly pack: make Windows build more robust. 11 years ago
os2 Make a number of changes to the OS/2 build. Submitter's comment below. 20 years ago
perl Add emacs cache files to .cvsignore. 18 years ago
shlib Apply mingw patches as supplied by Roumen Petrov an Alon Bar-Lev 15 years ago
ssl s3_cbc.c: make CBC_MAC_ROTATE_IN_PLACE universal. 10 years ago
test Fix for EXP-RC2-CBC-MD5 10 years ago
times Updates from 1.0.0-stable branch. 14 years ago
tools PR: 2234 13 years ago
util Add ordinal for CRYPTO_memcmp: since this will affect multiple 10 years ago
.cvsignore stop complaints about no CVS version 12 years ago
.gitignore More .gitignore adjustments. 11 years ago
ACKNOWLEDGMENTS missed change in ACKNOWLEDGEMENTS file 13 years ago
CHANGES correct CHANGES 11 years ago
CHANGES.SSLeay Updates from 1.0.0-stable branch. 14 years ago
Configure Configure: update linux-mips* lines. 11 years ago
FAQ FAQ/README: we are now using Git instead of CVS 10 years ago
INSTALL Fix URI of OpenSSL Request Tracker information 15 years ago
INSTALL.MacOS Typos (Chris Pepper <pepper@mail.reppep.com>) 22 years ago
INSTALL.NW Netware support. 16 years ago
INSTALL.OS2 Add support for shared libraries with OS/2. 21 years ago
INSTALL.VMS After some adjustments, apply the changes OpenSSL 1.0.0d on OpenVMS 12 years ago
INSTALL.W32 FAQ/README: we are now using Git instead of CVS 10 years ago
INSTALL.W64 Pull up Win64 support from 0.9.8. 18 years ago
INSTALL.WCE First draft for WCE PortSDK support. Once again! It's *draft* which requires 18 years ago
LICENSE OCSP stapling fix (OpenSSL 0.9.8r/1.0.0d) 13 years ago
Makefile.fips Print out an error for "make test" in FIPS builds. (from FIPS stable) 12 years ago
Makefile.org Make openssl verify return errors. 11 years ago
Makefile.shared Makefile.share: fix brown-bag typo in link_o.darwin. 13 years ago
NEWS update NEWS 11 years ago
PROBLEMS ./Configure: libcrypto.a can grow to many GB because of ar bug. 11 years ago
README FAQ/README: we are now using Git instead of CVS 10 years ago
README.ASN1 Merge from the ASN1 branch of new ASN1 code 23 years ago
README.ECC Add NSA sublicense info. 12 years ago
README.ENGINE oops, there were other cases of "ENGINE_ID" to change too. 21 years ago
README.FIPS Build fipscanister.o only by default. Utility build now needs 12 years ago
STATUS OCSP stapling fix (OpenSSL 0.9.8r/1.0.0d) 13 years ago
TABLE TABLE update. 11 years ago
config linux-pcc: make it more robust and recognize KERNEL_BITS variable. 11 years ago
e_os.h Improve WINCE support. 11 years ago
e_os2.h PR: 2563 12 years ago
install.com After some adjustments, apply the changes OpenSSL 1.0.0d on OpenVMS 12 years ago
makevms.com PR: 2730 11 years ago
openssl.doxy Add functions to add certs to stacks, used for CA file/path stuff in servers. 25 years ago
openssl.spec Fix from 0.9.8-stable 14 years ago


 OpenSSL 1.1.0-dev

 Copyright (c) 1998-2011 The OpenSSL Project
 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
 All rights reserved.


 The OpenSSL Project is a collaborative effort to develop a robust,
 commercial-grade, fully featured, and Open Source toolkit implementing the
 Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1)
 protocols as well as a full-strength general purpose cryptography 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 based on the excellent SSLeay library developed from Eric A. Young
 and Tim J. Hudson.  The OpenSSL toolkit is licensed under a dual-license (the
 OpenSSL license plus the SSLeay license) situation, which basically 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.


 The OpenSSL toolkit includes:

     Implementation of SSLv2, SSLv3, TLSv1 and the required code to support
     both SSLv2, SSLv3 and TLSv1 in the one server and client.

     General encryption and X.509 v1/v3 stuff needed by SSL/TLS but not
     actually logically part of it. It includes routines for the following:

        libdes - EAY's libdes DES encryption package which was floating
                 around the net for a few years, and was then relicensed by
                 him as part of SSLeay.  It includes 15 'modes/variations'
                 of DES (1, 2 and 3 key versions of ecb, cbc, cfb and ofb;
                 pcbc and a more general form of cfb and ofb) including desx
                 in cbc mode, a fast crypt(3), and routines to read
                 passwords from the keyboard.
        RC4 encryption,
        RC2 encryption      - 4 different modes, ecb, cbc, cfb and ofb.
        Blowfish encryption - 4 different modes, ecb, cbc, cfb and ofb.
        IDEA encryption     - 4 different modes, ecb, cbc, cfb and ofb.

        MD5 and MD2 message digest algorithms, fast implementations,
        SHA (SHA-0) and SHA-1 message digest algorithms,
        MDC2 message digest. A DES based hash that is popular on smart cards.

     Public Key
        RSA encryption/decryption/generation.
            There is no limit on the number of bits.
        DSA encryption/decryption/generation.
            There is no limit on the number of bits.
        Diffie-Hellman key-exchange/key generation.
            There is no limit on the number of bits.

     X.509v3 certificates
        X509 encoding/decoding into/from binary ASN1 and a PEM
             based ASCII-binary encoding which supports encryption with a
             private key.  Program to generate RSA and DSA certificate
             requests and to generate RSA and DSA certificates.

        The normal digital envelope routines and base64 encoding.  Higher
        level access to ciphers and digests by name.  New ciphers can be
        loaded at run time.  The BIO io system which is a simple non-blocking
        IO abstraction.  Current methods supported are file descriptors,
        sockets, socket accept, socket connect, memory buffer, buffering, SSL
        client/server, file pointer, encryption, digest, non-blocking testing
        and null.

     Data structures
        A dynamically growing hashing system
        A simple stack.
        A Configuration loader that uses a format similar to MS .ini files.

     A command line tool that can be used for:
        Creation of RSA, DH and DSA key parameters
        Creation of X.509 certificates, CSRs and CRLs
        Calculation of Message Digests
        Encryption and Decryption with Ciphers
        SSL/TLS Client and Server Tests
        Handling of S/MIME signed or encrypted mail


 Various companies hold various patents for various algorithms in various
 locations around the world. _YOU_ are responsible for ensuring that your use
 of any algorithms is legal by checking if there are any patents in your
 country.  The file contains some of the patents that we know about or are
 rumored to exist. This is not a definitive list.

 RSA Security holds software patents on the RC5 algorithm.  If you
 intend to use this cipher, you must contact RSA Security for
 licensing conditions. Their web page is http://www.rsasecurity.com/.

 RC4 is a trademark of RSA Security, so use of this label should perhaps
 only be used with RSA Security's permission.

 The IDEA algorithm is patented by Ascom in Austria, France, Germany, Italy,
 Japan, the Netherlands, Spain, Sweden, Switzerland, UK and the USA.  They
 should be contacted if that algorithm is to be used; their web page is

 NTT and Mitsubishi have patents and pending patents on the Camellia
 algorithm, but allow use at no charge without requiring an explicit
 licensing agreement: http://info.isl.ntt.co.jp/crypt/eng/info/chiteki.html


 To install this package under a Unix derivative, read the INSTALL file.  For
 a Win32 platform, read the INSTALL.W32 file.  For OpenVMS systems, read

 Read the documentation in the doc/ directory.  It is quite rough, but it
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.


 For some platforms, there are some known problems that may affect the user
 or application author.  We try to collect those in doc/PROBLEMS, with current
 thoughts on how they should be solved in a future of OpenSSL.


 See the OpenSSL website www.openssl.org for details of how to obtain
 commercial technical support.

 If you have any problems with OpenSSL then please take the following steps

    - 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)

 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/support/rt.html) by mail to:


 Note that the request tracker should NOT be used 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.

 Note that mail to openssl-bugs@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
 mailing list. Confidential mail may be sent to openssl-security@openssl.org
 (PGP key available from the key servers).


 Development is coordinated on the openssl-dev mailing list (see
 http://www.openssl.org for information on subscribing). If you
 would like to submit a patch, send it to openssl-bugs@openssl.org with
 the string "[PATCH]" in the subject. Please be sure to include a
 textual explanation of what your patch does.

 If you are unsure as to whether a feature will be useful for the general
 OpenSSL community please discuss it on the openssl-dev mailing list first.
 Someone may be already working on the same thing or there may be a good
 reason as to why that feature isn't implemented.

 Patches should be as up to date as possible, preferably relative to the
 current Git or the last snapshot. They should follow the coding style of
 OpenSSL and compile without warnings. Some of the core team developer targets
 can be used for testing purposes, (debug-steve64, debug-geoff etc). OpenSSL
 compiles on many varied platforms: try to ensure you only use portable

 Note: For legal reasons, contributions from the US can be accepted only
 if a TSU notification and a copy of the patch are sent to crypt@bis.doc.gov
 (formerly BXA) with a copy to the ENC Encryption Request Coordinator;
 please take some time to look at
    http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
    http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e))
 for the details. If "your encryption source code is too large to serve as
 an email attachment", they are glad to receive it by fax instead; hope you
 have a cheap long-distance plan.

 Our preferred format for changes is "diff -u" output. You might
 generate it like this:

 # cd openssl-work
 # [your changes]
 # ./Configure dist; make clean
 # cd ..
 # diff -ur openssl-orig openssl-work > mydiffs.patch