TLS/SSL and crypto library
Find a file
Richard Levitte 1f1f23a882 Fix from main trunk, 2000-09-25 13:12 levitte:
Document the change.
2000-10-11 02:28:39 +00:00
apps More code for X509_print_ex() support. 2000-10-06 11:51:47 +00:00
bugs Fix for Netscape "hang" bug. 2000-02-15 14:19:44 +00:00
certs Fix a bug in the modified purpose code: it wasn't updated to use the 1999-12-03 00:53:48 +00:00
crypto Fix from main trunk, 2000-09-25 10:52 levitte: 2000-10-11 02:04:16 +00:00
demos Two new PKCS#12 demo programs. 2000-09-07 23:14:26 +00:00
doc Fix from main trunk, 2000-09-25 07:55 ulf: 2000-10-11 01:56:00 +00:00
include Add include dir 1998-12-23 07:55:37 +00:00
MacOS MacOS pseudo-random entropy collector. 2000-02-29 15:18:46 +00:00
ms Fix from main trunk, 2000-09-25 11:30 levitte: 2000-10-11 02:22:59 +00:00
perl Remove obsolete files. 1999-07-22 21:57:41 +00:00
rsaref Fix from main trunk, 2000-09-25 10:52 levitte: 2000-10-11 02:04:16 +00:00
shlib A couple of corrections concerning HPUX 10 and shared libraries. 2000-03-24 16:06:22 +00:00
ssl Fix from main trunk, 2000-09-25 10:52 levitte: 2000-10-11 02:04:16 +00:00
test Synchronise the VMS build with the Unix one. 2000-09-08 20:25:49 +00:00
times I forgot this file that Assar provided as well... 2000-08-14 14:20:52 +00:00
tools Fix c_rehash script, add -fingerprint option to crl. 2000-05-18 00:33:00 +00:00
util Fix from main trunk, 2000-09-25 12:22 levitte: 2000-10-11 02:27:07 +00:00
VMS It's not just VMS that needs some symbols to be hacked. Let's 2000-09-07 08:18:05 +00:00
.cvsignore Redo and enhance the support for building shared libraries. Currently 2000-07-21 15:08:53 +00:00
CHANGES Fix from main trunk, 2000-09-25 13:12 levitte: 2000-10-11 02:28:39 +00:00
CHANGES.SSLeay *** empty log message *** 1998-12-23 07:42:26 +00:00
config Portability patch for HP MPE/iX. Submitted by Mark Bixby <mark_bixby@hp.com> 2000-09-21 05:42:01 +00:00
Configure Make sure that shareable libraries are turned off if we don't know how 2000-10-09 00:48:30 +00:00
e_os.h Remove what was described by someone as "an EAY hack for compiling 2000-10-01 21:28:07 +00:00
e_os2.h In Message-ID: <003201bfb332$14a07520$0801a8c0@janm.transactionsite.com>, 2000-05-02 12:16:01 +00:00
FAQ Time to build the release. Bump the version info accordingly. 2000-09-24 15:21:30 +00:00
INSTALL Clarify how one should behave when make fails. The fault is not 2000-09-08 22:19:27 +00:00
install.com Make sure installed files are world readable 1999-11-12 01:42:59 +00:00
INSTALL.MacOS Further work on MacOS port. See INSTALL.MacOS for details. 2000-01-05 21:06:56 +00:00
INSTALL.VMS Inform the VMS people that RSAref is no longer needed 2000-09-17 11:57:33 +00:00
INSTALL.W32 URL to "latest" Mingw release (which is almost a year old :() 2000-09-23 02:06:08 +00:00
LICENSE Increase the year by one. 2000-01-27 19:28:49 +00:00
Makefile.org Make sure ranlib is only used on .a libraries. 2000-10-09 00:50:04 +00:00
makevms.com Remove engine stuff that was erroneously put in the main trunk. 2000-09-14 18:16:25 +00:00
NEWS spelling 2000-09-23 19:08:16 +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 Linux on Alpha has the configuration name linux-alpha-gcc, not 2000-10-08 19:38:28 +00:00
README Update the status and version number to 0.9.7-dev. 2000-09-24 17:31:37 +00:00
README.ENGINE Change the Windows building scripts to enable DSO_WIN32. 2000-09-24 14:48:51 +00:00
STATUS Update the status and version number to 0.9.7-dev. 2000-09-24 17:31:37 +00:00
TABLE make update 2000-09-24 14:54:31 +00:00

 OpenSSL 0.9.6 24 Sep 2000

 Copyright (c) 1998-2000 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 (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. 

 OVERVIEW
 --------

 The OpenSSL toolkit includes:

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

 libcrypto.a:
     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:

     Ciphers
        libdes - EAY's libdes DES encryption package which has been floating
                 around the net for a few years.  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.

     Digests
        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.

     Systems
        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.

 openssl: 
     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

        
 PATENTS
 -------

 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
 rumoured 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, Netherlands, Spain, Sweden, Switzerland, UK and the USA.  They should
 be contacted if that algorithm is to be used, their web page is
 http://www.ascom.ch/.

 INSTALLATION
 ------------

 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
 INSTALL.VMS.

 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 used them. Look at the example programs.

 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)

 Report the bug to the OpenSSL project at:

    openssl-bugs@openssl.org

 Note that mail to openssl-bugs@openssl.org is forwarded to a public
 mailing list. Confidential mail may be sent to openssl-security@openssl.org
 (PGP key available from the key servers).

 HOW TO CONTRIBUTE TO OpenSSL
 ----------------------------

 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-dev@openssl.org with
 the string "[PATCH]" in the subject. Please be sure to include a
 textual explanation of what your patch does.

 Note: For legal reasons, contributions from the US can be accepted only
 if a copy of the patch is sent to crypt@bxa.doc.gov

 The 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