head	1.9;
access;
symbols
	RELENG_8_4:1.9.0.2
	RELENG_9_1_0_RELEASE:1.6.2.1
	RELENG_9_1:1.6.2.1.0.2
	RELENG_9_1_BP:1.6.2.1
	RELENG_8_3_0_RELEASE:1.2.2.3
	RELENG_8_3:1.2.2.3.0.4
	RELENG_8_3_BP:1.2.2.3
	RELENG_9_0_0_RELEASE:1.6
	RELENG_9_0:1.6.0.4
	RELENG_9_0_BP:1.6
	RELENG_9:1.6.0.2
	RELENG_9_BP:1.6
	RELENG_7_4_0_RELEASE:1.1.1.18.2.2
	RELENG_8_2_0_RELEASE:1.2.2.3
	RELENG_7_4:1.1.1.18.2.2.0.2
	RELENG_7_4_BP:1.1.1.18.2.2
	RELENG_8_2:1.2.2.3.0.2
	RELENG_8_2_BP:1.2.2.3
	RELENG_8_1_0_RELEASE:1.2.2.1
	RELENG_8_1:1.2.2.1.0.2
	RELENG_8_1_BP:1.2.2.1
	RELENG_7_3_0_RELEASE:1.1.1.18
	RELENG_7_3:1.1.1.18.0.10
	RELENG_7_3_BP:1.1.1.18
	RELENG_8_0_0_RELEASE:1.2
	RELENG_8_0:1.2.0.4
	RELENG_8_0_BP:1.2
	RELENG_8:1.2.0.2
	RELENG_8_BP:1.2
	RELENG_7_2_0_RELEASE:1.1.1.18
	RELENG_7_2:1.1.1.18.0.8
	RELENG_7_2_BP:1.1.1.18
	RELENG_7_1_0_RELEASE:1.1.1.18
	RELENG_6_4_0_RELEASE:1.1.1.15
	RELENG_7_1:1.1.1.18.0.6
	RELENG_7_1_BP:1.1.1.18
	RELENG_6_4:1.1.1.15.0.12
	RELENG_6_4_BP:1.1.1.15
	RELENG_7_0_0_RELEASE:1.1.1.18
	RELENG_6_3_0_RELEASE:1.1.1.15
	RELENG_7_0:1.1.1.18.0.4
	RELENG_7_0_BP:1.1.1.18
	RELENG_6_3:1.1.1.15.0.10
	RELENG_6_3_BP:1.1.1.15
	RELENG_7:1.1.1.18.0.2
	RELENG_7_BP:1.1.1.18
	v0_9_8e:1.1.1.18
	RELENG_6_2_0_RELEASE:1.1.1.15
	RELENG_6_2:1.1.1.15.0.8
	RELENG_6_2_BP:1.1.1.15
	v0_9_8d:1.1.1.17
	v0_9_8b:1.1.1.16
	RELENG_5_5_0_RELEASE:1.1.1.14.2.1
	RELENG_5_5:1.1.1.14.2.1.0.4
	RELENG_5_5_BP:1.1.1.14.2.1
	RELENG_6_1_0_RELEASE:1.1.1.15
	RELENG_6_1:1.1.1.15.0.6
	RELENG_6_1_BP:1.1.1.15
	RELENG_6_0_0_RELEASE:1.1.1.15
	RELENG_6_0:1.1.1.15.0.4
	RELENG_6_0_BP:1.1.1.15
	RELENG_6:1.1.1.15.0.2
	RELENG_6_BP:1.1.1.15
	RELENG_5_4_0_RELEASE:1.1.1.14.2.1
	RELENG_5_4:1.1.1.14.2.1.0.2
	RELENG_5_4_BP:1.1.1.14.2.1
	v0_9_7e:1.1.1.15
	RELENG_4_11_0_RELEASE:1.1.1.1.2.9
	RELENG_4_11:1.1.1.1.2.9.0.4
	RELENG_4_11_BP:1.1.1.1.2.9
	RELENG_5_3_0_RELEASE:1.1.1.14
	RELENG_5_3:1.1.1.14.0.4
	RELENG_5_3_BP:1.1.1.14
	RELENG_5:1.1.1.14.0.2
	RELENG_5_BP:1.1.1.14
	RELENG_4_10_0_RELEASE:1.1.1.1.2.9
	RELENG_4_10:1.1.1.1.2.9.0.2
	RELENG_4_10_BP:1.1.1.1.2.9
	v0_9_7d:1.1.1.14
	RELENG_5_2_1_RELEASE:1.1.1.13
	RELENG_5_2_0_RELEASE:1.1.1.13
	RELENG_5_2:1.1.1.13.0.2
	RELENG_5_2_BP:1.1.1.13
	RELENG_4_9_0_RELEASE:1.1.1.1.2.8
	RELENG_4_9:1.1.1.1.2.8.0.2
	RELENG_4_9_BP:1.1.1.1.2.8
	v0_9_7c:1.1.1.13
	RELENG_5_1_0_RELEASE:1.1.1.12
	RELENG_5_1:1.1.1.12.0.2
	RELENG_5_1_BP:1.1.1.12
	RELENG_4_8_0_RELEASE:1.1.1.1.2.7
	RELENG_4_8:1.1.1.1.2.7.0.2
	RELENG_4_8_BP:1.1.1.1.2.7
	v0_9_7a:1.1.1.12
	v0_9_7:1.1.1.11
	RELENG_5_0_0_RELEASE:1.1.1.10
	RELENG_5_0:1.1.1.10.0.2
	RELENG_5_0_BP:1.1.1.10
	RELENG_4_7_0_RELEASE:1.1.1.1.2.5
	RELENG_4_7:1.1.1.1.2.5.0.2
	RELENG_4_7_BP:1.1.1.1.2.5
	RELENG_4_6_2_RELEASE:1.1.1.1.2.3.6.1
	v0_9_6g:1.1.1.10
	v0_9_6f:1.1.1.9
	v0_9_6e:1.1.1.8
	v0_9_6d:1.1.1.7
	RELENG_4_6_1_RELEASE:1.1.1.1.2.3
	RELENG_4_6_0_RELEASE:1.1.1.1.2.3
	RELENG_4_6:1.1.1.1.2.3.0.6
	RELENG_4_6_BP:1.1.1.1.2.3
	RELENG_4_5_0_RELEASE:1.1.1.1.2.3
	v0_9_6c:1.1.1.6
	RELENG_4_5:1.1.1.1.2.3.0.4
	RELENG_4_5_BP:1.1.1.1.2.3
	RELENG_4_4_0_RELEASE:1.1.1.1.2.3
	RELENG_4_4:1.1.1.1.2.3.0.2
	RELENG_4_4_BP:1.1.1.1.2.3
	v0_9_6b:1.1.1.5
	v0_9_6a:1.1.1.4
	RELENG_4_3_0_RELEASE:1.1.1.1.2.2
	RELENG_4_3:1.1.1.1.2.2.0.2
	RELENG_4_3_BP:1.1.1.1.2.2
	v0_9_6_2001_02_10:1.1.1.3
	RELENG_4_2_0_RELEASE:1.1.1.1.2.1
	v0_9_6:1.1.1.3
	RELENG_4_1_1_RELEASE:1.1.1.1.2.1
	PRE_SMPNG:1.1.1.2
	RELENG_4_1_0_RELEASE:1.1.1.1
	v0_9_5a:1.1.1.2
	RELENG_4_0_0_RELEASE:1.1.1.1
	RELENG_4:1.1.1.1.0.2
	RELENG_4_BP:1.1.1.1
	v0_9_4:1.1.1.1
	OPENSSL:1.1.1;
locks; strict;
comment	@# @;


1.9
date	2013.02.14.01.22.09;	author svnexp;	state Exp;
branches
	1.9.2.1;
next	1.8;

1.8
date	2012.07.12.19.30.53;	author jkim;	state Exp;
branches;
next	1.7;

1.7
date	2012.06.27.18.44.36;	author jkim;	state Exp;
branches;
next	1.6;

1.6
date	2010.12.03.22.59.54;	author simon;	state Exp;
branches
	1.6.2.1
	1.6.4.1;
next	1.5;

1.5
date	2010.11.22.18.23.44;	author simon;	state Exp;
branches;
next	1.4;

1.4
date	2010.04.01.15.19.51;	author simon;	state Exp;
branches;
next	1.3;

1.3
date	2010.03.13.19.22.41;	author simon;	state Exp;
branches;
next	1.2;

1.2
date	2009.06.14.19.45.16;	author simon;	state Exp;
branches
	1.2.2.1;
next	1.1;

1.1
date	2000.01.10.06.21.17;	author kris;	state Exp;
branches
	1.1.1.1;
next	;

1.9.2.1
date	2013.02.14.01.22.09;	author svnexp;	state dead;
branches;
next	1.9.2.2;

1.9.2.2
date	2013.03.28.13.02.27;	author svnexp;	state Exp;
branches;
next	;

1.6.2.1
date	2012.07.02.16.00.38;	author jkim;	state Exp;
branches
	1.6.2.1.2.1;
next	1.6.2.2;

1.6.2.2
date	2013.03.14.19.04.07;	author svnexp;	state Exp;
branches;
next	;

1.6.2.1.2.1
date	2013.04.02.18.10.50;	author svnexp;	state Exp;
branches;
next	;

1.6.4.1
date	2013.04.02.18.17.57;	author svnexp;	state Exp;
branches;
next	;

1.2.2.1
date	2010.05.22.18.40.54;	author simon;	state Exp;
branches;
next	1.2.2.2;

1.2.2.2
date	2010.11.26.22.50.58;	author simon;	state Exp;
branches;
next	1.2.2.3;

1.2.2.3
date	2010.12.09.22.03.53;	author simon;	state Exp;
branches
	1.2.2.3.4.1;
next	1.2.2.4;

1.2.2.4
date	2012.07.02.16.14.35;	author jkim;	state Exp;
branches;
next	1.2.2.5;

1.2.2.5
date	2013.03.08.20.22.35;	author svnexp;	state Exp;
branches;
next	;

1.2.2.3.4.1
date	2013.04.02.17.48.59;	author svnexp;	state Exp;
branches;
next	;

1.1.1.1
date	2000.01.10.06.21.17;	author kris;	state Exp;
branches
	1.1.1.1.2.1;
next	1.1.1.2;

1.1.1.2
date	2000.04.13.06.24.51;	author kris;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2000.11.13.00.54.39;	author kris;	state Exp;
branches;
next	1.1.1.4;

1.1.1.4
date	2001.05.20.03.04.55;	author kris;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	2001.07.19.19.57.20;	author kris;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	2002.01.27.03.10.44;	author kris;	state Exp;
branches;
next	1.1.1.7;

1.1.1.7
date	2002.07.30.12.43.18;	author nectar;	state Exp;
branches;
next	1.1.1.8;

1.1.1.8
date	2002.07.30.13.37.25;	author nectar;	state Exp;
branches;
next	1.1.1.9;

1.1.1.9
date	2002.08.10.01.37.51;	author nectar;	state Exp;
branches;
next	1.1.1.10;

1.1.1.10
date	2002.08.10.01.47.55;	author nectar;	state Exp;
branches
	1.1.1.10.2.1;
next	1.1.1.11;

1.1.1.11
date	2003.01.28.21.10.10;	author markm;	state Exp;
branches;
next	1.1.1.12;

1.1.1.12
date	2003.02.19.23.11.04;	author nectar;	state Exp;
branches;
next	1.1.1.13;

1.1.1.13
date	2003.10.01.12.32.37;	author nectar;	state Exp;
branches;
next	1.1.1.14;

1.1.1.14
date	2004.03.17.15.41.44;	author nectar;	state Exp;
branches
	1.1.1.14.2.1;
next	1.1.1.15;

1.1.1.15
date	2005.02.25.05.32.21;	author nectar;	state Exp;
branches;
next	1.1.1.16;

1.1.1.16
date	2006.07.29.19.10.15;	author simon;	state Exp;
branches;
next	1.1.1.17;

1.1.1.17
date	2006.10.01.07.33.40;	author simon;	state Exp;
branches;
next	1.1.1.18;

1.1.1.18
date	2007.03.15.20.02.19;	author simon;	state Exp;
branches
	1.1.1.18.2.1;
next	;

1.1.1.1.2.1
date	2000.08.20.08.45.57;	author kris;	state Exp;
branches;
next	1.1.1.1.2.2;

1.1.1.1.2.2
date	2000.11.26.11.32.45;	author kris;	state Exp;
branches;
next	1.1.1.1.2.3;

1.1.1.1.2.3
date	2001.07.04.23.19.08;	author kris;	state Exp;
branches
	1.1.1.1.2.3.2.1
	1.1.1.1.2.3.4.1
	1.1.1.1.2.3.6.1;
next	1.1.1.1.2.4;

1.1.1.1.2.4
date	2002.07.30.22.04.59;	author nectar;	state Exp;
branches;
next	1.1.1.1.2.5;

1.1.1.1.2.5
date	2002.08.11.14.13.53;	author nectar;	state Exp;
branches
	1.1.1.1.2.5.2.1;
next	1.1.1.1.2.6;

1.1.1.1.2.6
date	2003.02.14.22.37.38;	author nectar;	state Exp;
branches;
next	1.1.1.1.2.7;

1.1.1.1.2.7
date	2003.02.20.15.07.20;	author nectar;	state Exp;
branches;
next	1.1.1.1.2.8;

1.1.1.1.2.8
date	2003.10.03.01.32.04;	author nectar;	state Exp;
branches;
next	1.1.1.1.2.9;

1.1.1.1.2.9
date	2004.04.02.01.10.59;	author nectar;	state Exp;
branches;
next	;

1.1.1.1.2.3.2.1
date	2002.07.31.16.40.31;	author nectar;	state Exp;
branches;
next	;

1.1.1.1.2.3.4.1
date	2002.07.31.14.04.47;	author nectar;	state Exp;
branches;
next	;

1.1.1.1.2.3.6.1
date	2002.07.31.02.54.37;	author nectar;	state Exp;
branches;
next	1.1.1.1.2.3.6.2;

1.1.1.1.2.3.6.2
date	2003.02.21.16.32.47;	author nectar;	state Exp;
branches;
next	;

1.1.1.1.2.5.2.1
date	2003.02.20.20.42.05;	author nectar;	state Exp;
branches;
next	;

1.1.1.10.2.1
date	2003.02.20.17.14.09;	author nectar;	state Exp;
branches;
next	;

1.1.1.14.2.1
date	2005.03.01.16.47.24;	author nectar;	state Exp;
branches;
next	;

1.1.1.18.2.1
date	2010.11.28.13.45.51;	author simon;	state Exp;
branches;
next	1.1.1.18.2.2;

1.1.1.18.2.2
date	2010.12.09.22.05.16;	author simon;	state Exp;
branches;
next	1.1.1.18.2.3;

1.1.1.18.2.3
date	2012.07.02.16.24.43;	author jkim;	state Exp;
branches;
next	;


desc
@@


1.9
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/246772
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@
 OpenSSL 1.0.1e 11 Feb 2013

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

     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
 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
 http://www.ascom.ch/.

 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

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

 PROBLEMS
 --------

 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.

 SUPPORT
 -------

 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
 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 via the Request Tracker
 (http://www.openssl.org/support/rt.html) by mail to:

    openssl-bugs@@openssl.org

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

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

 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]
 and
    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

@


1.9.2.1
log
@file README was added on branch RELENG_8_4 on 2013-03-28 13:02:27 +0000
@
text
@d1 218
@


1.9.2.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 218

 OpenSSL 0.9.8y 5 Feb 2013

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

     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
 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
 http://www.ascom.ch/.

 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

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

 PROBLEMS
 --------

 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.

 SUPPORT
 -------

 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
 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 via the Request Tracker
 (http://www.openssl.org/support/rt.html) by mail to:

    openssl-bugs@@openssl.org

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

 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-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 CVS 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
 features.

 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]
 and
    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

@


1.8
log
@SVN rev 238405 on 2012-07-12 19:30:53Z by jkim

Merge OpenSSL 1.0.1c.

Approved by:	benl (maintainer)
@
text
@d2 1
a2 1
 OpenSSL 1.0.1c 10 May 2012
d193 1
a193 1
 current CVS or the last snapshot. They should follow the coding style of
@


1.7
log
@SVN rev 237657 on 2012-06-27 18:44:36Z by jkim

Merge OpenSSL 0.9.8x.

Reviewed by:	stas
Approved by:	benl (maintainer)
MFC after:	3 days
@
text
@d2 1
a2 1
 OpenSSL 0.9.8x 10 May 2012
@


1.6
log
@SVN rev 216166 on 2010-12-03 22:59:54Z by simon

Merge OpenSSL 0.9.8q into head.

Security:	CVE-2010-4180
Security:	http://www.openssl.org/news/secadv_20101202.txt
MFC after:	3 days
@
text
@d2 1
a2 1
 OpenSSL 0.9.8q 2 Dec 2010
d4 1
a4 1
 Copyright (c) 1998-2009 The OpenSSL Project
@


1.6.4.1
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/249029
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@d2 1
a2 1
 OpenSSL 0.9.8y 5 Feb 2013
d4 1
a4 1
 Copyright (c) 1998-2011 The OpenSSL Project
@


1.6.2.1
log
@SVN rev 237998 on 2012-07-02 16:00:38Z by jkim

MFC:	r237657, r237658, r237666

Merge OpenSSL 0.9.8x and regen manual pages.
@
text
@d2 1
a2 1
 OpenSSL 0.9.8x 10 May 2012
d4 1
a4 1
 Copyright (c) 1998-2011 The OpenSSL Project
@


1.6.2.1.2.1
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/249029
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@d2 1
a2 1
 OpenSSL 0.9.8y 5 Feb 2013
@


1.6.2.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248272
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@d2 1
a2 1
 OpenSSL 0.9.8y 5 Feb 2013
@


1.5
log
@SVN rev 215697 on 2010-11-22 18:23:44Z by simon

Merge OpenSSL 0.9.8p into head.

Security:	CVE-2010-3864
Security:	http://www.openssl.org/news/secadv_20101116.txt
@
text
@d2 1
a2 1
 OpenSSL 0.9.8p 16 Nov 2010
@


1.4
log
@SVN rev 206046 on 2010-04-01 15:19:51Z by simon

Merge OpenSSL 0.9.8n into head.

This fixes CVE-2010-0740 which only affected -CURRENT (OpenSSL 0.9.8m)
but not -STABLE branches.

I have not yet been able to find out if CVE-2010-0433 impacts FreeBSD.
This will be investigated further.

Security:	CVE-2010-0433, CVE-2010-0740
Security:	http://www.openssl.org/news/secadv_20100324.txt
@
text
@d2 1
a2 1
 OpenSSL 0.9.8n
@


1.3
log
@SVN rev 205128 on 2010-03-13 19:22:41Z by simon

Merge OpenSSL 0.9.8m into head.

This also "reverts" some FreeBSD local changes so we should now
be back to using entirely stock OpenSSL.  The local changes were
simple $FreeBSD$ lines additions, which were required in the CVS
days, and the patch for FreeBSD-SA-09:15.ssl which has been
superseded with OpenSSL 0.9.8m's RFC5746 'TLS renegotiation
extension' support.

MFC after:	3 weeks
@
text
@d2 1
a2 1
 OpenSSL 0.9.8m
@


1.2
log
@SVN rev 194206 on 2009-06-14 19:45:16Z by simon

Merge OpenSSL 0.9.8k into head.

Approved by:	re
@
text
@d2 1
a2 1
 OpenSSL 0.9.8k
d4 1
a4 1
 Copyright (c) 1998-2008 The OpenSSL Project
a114 2
 The MDC2 algorithm is patented by IBM.

d140 3
d169 4
d183 1
a183 1
 would like to submit a patch, send it to openssl-dev@@openssl.org with
d187 12
@


1.2.2.1
log
@SVN rev 208419 on 2010-05-22 18:40:54Z by simon

Merge OpenSSL 0.9.8n from head into stable/8.

Approved by:	re (kib)
@
text
@d2 1
a2 1
 OpenSSL 0.9.8n
d4 1
a4 1
 Copyright (c) 1998-2009 The OpenSSL Project
d115 2
a141 3
 See the OpenSSL website www.openssl.org for details of how to obtain
 commercial technical support.

a167 4
 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.

d178 1
a178 1
 would like to submit a patch, send it to openssl-bugs@@openssl.org with
a181 12
 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 CVS 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
 features.

@


1.2.2.2
log
@SVN rev 215912 on 2010-11-26 22:50:58Z by simon

Merge OpenSSL 0.9.8p into stable/8.

This merges up to and including head/crypto/openssl/ r215697; and
head/secure/lib/libcrypto/, head/secure/lib/libssl/,
head/secure/usr.bin/openssl/ r215698.

To make the merge simpler, a hack was added to set MACHINE_CPUARCH.

Security:	CVE-2010-2939, CVE-2010-3864
Security:	http://www.openssl.org/news/secadv_20101116.txt
Security:	FreeBSD-SA-10:10.openssl
Approved by:	re (implicitly - they did not object of the general idea
		of OpenSSL update)
@
text
@d2 1
a2 1
 OpenSSL 0.9.8p 16 Nov 2010
@


1.2.2.3
log
@SVN rev 216341 on 2010-12-09 22:03:53Z by simon

MFC r216166, r216167:

Merge in OpenSSL 0.9.8q.

Approved by:	re (kib)
Security:	CVE-2010-4180
Security:	http://www.openssl.org/news/secadv_20101202.txt
@
text
@d2 1
a2 1
 OpenSSL 0.9.8q 2 Dec 2010
@


1.2.2.3.4.1
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/249029
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@d2 1
a2 1
 OpenSSL 0.9.8y 5 Feb 2013
d4 1
a4 1
 Copyright (c) 1998-2011 The OpenSSL Project
@


1.2.2.4
log
@SVN rev 237999 on 2012-07-02 16:14:35Z by jkim

MFC:	r237657, r237658, r237666

Merge OpenSSL 0.9.8x and regen manual pages.
@
text
@d2 1
a2 1
 OpenSSL 0.9.8x 10 May 2012
d4 1
a4 1
 Copyright (c) 1998-2011 The OpenSSL Project
@


1.2.2.5
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248057
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@d2 1
a2 1
 OpenSSL 0.9.8y 5 Feb 2013
@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
 OpenSSL 0.9.4  09 Aug 1999
d4 1
a4 1
 Copyright (c) 1998-1999 The OpenSSL Project
d14 4
a17 3
 protocols with full-strength cryptography world-wide. 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. 
d23 1
a23 1
 purposes as long as you fulfill the conditions of both licenses. 
d39 7
a45 6
        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.
d57 1
a57 1
        RSA encryption/decryption/generation.  
d59 1
a59 1
        DSA encryption/decryption/generation.   
d61 1
a61 1
        Diffie-Hellman key-exchange/key generation.  
d66 1
a66 1
             based ascii-binary encoding which supports encryption with a
d84 9
a92 2
 openssl: 
     A command line tool which provides the following functions:
a93 33
     enc     - a general encryption program that can encrypt/decrypt using
               one of 17 different cipher/mode combinations.  The
               input/output can also be converted to/from base64
               ascii encoding.
     dgst    - a generate message digesting program that will generate
               message digests for any of md2, md5, sha (sha-0 or sha-1)
               or mdc2.
     asn1parse - parse and display the structure of an asn1 encoded
               binary file.
     rsa     - Manipulate RSA private keys.
     dsa     - Manipulate DSA private keys.
     dh      - Manipulate Diffie-Hellman parameter files.
     dsaparam- Manipulate and generate DSA parameter files.
     crl     - Manipulate certificate revocation lists.
     crt2pkcs7- Generate a pkcs7 object containing a crl and a certificate.
     x509    - Manipulate x509 certificates, self-sign certificates.
     req     - Manipulate PKCS#10 certificate requests and also
               generate certificate requests.
     genrsa  - Generates an arbitrary sized RSA private key.
     gendsa  - Generates DSA parameters.
     gendh   - Generates a set of Diffie-Hellman parameters, the prime
               will be a strong prime.
     ca      - Create certificates from PKCS#10 certificate requests.
               This program also maintains a database of certificates
               issued.
     verify  - Check x509 certificate signatures.
     speed   - Benchmark OpenSSL's ciphers.
     s_server- A test SSL server.
     s_client- A test SSL client.
     s_time  - Benchmark SSL performance of SSL server programs.
     errstr  - Convert from OpenSSL hex error codes to a readable form.
     nseq    - Netscape certificate sequence utility
        
d101 1
a101 1
 rumoured to exist. This is not a definitive list.
d103 3
a105 4
 RSA Data Security holds software patents on the RSA and RC5 algorithms.  If
 their ciphers are used used inside the USA (and Japan?), you must contact RSA
 Data Security for licensing conditions. Their web page is
 http://www.rsa.com/.
d107 2
a108 2
 RC4 is a trademark of RSA Data Security, so use of this label should perhaps
 only be used with RSA Data Security's permission. 
d111 2
a112 2
 Japan, Netherlands, Spain, Sweden, Switzerland, UK and the USA.  They should
 be contacted if that algorithm is to be used, their web page is
d115 6
d128 3
a130 2
 For people in the USA, it is possible to compile OpenSSL to use RSA Inc.'s
 public key library, RSAREF, by configuring OpenSSL with the option "rsaref".
d132 6
a137 3
 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.
d139 1
a139 1
 SUPPORT 
d145 2
d148 1
a148 3
    - Remove compiler optimisation flags 
    - Add compiler debug flags (if using gcc then remove -fomit-frame-pointer
      before you try to debug things)
d153 9
a161 16
    OpenSSL Details
    - Version, most of these details can be got from the
      'openssl version -a' command.
    Operating System Details
    - On Unix systems: Output of './config -t'
    - OS Name, Version
    - Hardware platform
    Compiler Details
    - Name
    - Version
    Application Details 
    - Name 
    - Version 
    Problem Description
    - include steps that will reproduce the problem (if known)
    Stack Traceback (if the application dumps core)
d163 2
a164 1
 Report the bug to the OpenSSL project at:
d168 5
d178 14
a191 3
 would like to submit a patch, send it to openssl-dev@@openssl.org.
 Please be sure to include a textual explanation of what your patch
 does.
d193 1
a193 1
 The preferred format for changes is "diff -u" output. You might
d200 2
a201 1
 # diff -urN openssl-orig openssl-work > mydiffs.patch
@


1.1.1.1
log
@Initial import of OpenSSL 0.9.4, sans IDEA and RSA code for patent
infringement reasons.
@
text
@@


1.1.1.1.2.1
log
@MFC: OpenSSL 0.9.5a
@
text
@d2 1
a2 1
 OpenSSL 0.9.5a  1 Apr 2000
d4 1
a4 1
 Copyright (c) 1998-2000 The OpenSSL Project
d14 3
a16 4
 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. 
d83 1
a83 7
     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
d85 32
a159 2
    - Download the current snapshot from ftp://ftp.openssl.org/snapshot/
      to see if the problem has already been addressed
d162 2
d168 16
a183 9
    - 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)
a188 4
 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).

d194 3
a196 3
 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.
@


1.1.1.1.2.2
log
@MFC: OpenSSL 0.9.6
@
text
@d2 1
a2 1
 OpenSSL 0.9.6 24 Sep 2000
d102 4
a105 3
 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/.
d107 2
a108 2
 RC4 is a trademark of RSA Security, so use of this label should perhaps
 only be used with RSA Security's permission. 
d122 3
a169 3
 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

d177 1
a177 1
 # diff -ur openssl-orig openssl-work > mydiffs.patch
@


1.1.1.1.2.3
log
@MFC: Update to OpenSSL 0.9.6a
@
text
@d2 1
a2 1
 OpenSSL 0.9.6a 5 Apr 2001
@


1.1.1.1.2.3.2.1
log
@MFC: OpenSSL 0.9.6e
@
text
@d2 1
a2 1
 OpenSSL 0.9.6e 30 July 2002
d4 1
a4 1
 Copyright (c) 1998-2002 The OpenSSL Project
d65 1
a65 1
             based ASCII-binary encoding which supports encryption with a
d100 1
a100 1
 rumored to exist. This is not a definitive list.
d110 2
a111 2
 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
d122 2
a123 9
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.

 PROBLEMS
 --------

 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.
d149 1
a149 2
 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/rt2.html) by mail to:
d153 1
a153 2
 Note that mail to openssl-bugs@@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
d167 1
a167 3
 if a TSA notification and a copy of the patch is sent to crypt@@bis.doc.gov;
 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
@


1.1.1.1.2.3.4.1
log
@MFC: OpenSSL 0.9.6e
@
text
@d2 1
a2 1
 OpenSSL 0.9.6e 30 July 2002
d4 1
a4 1
 Copyright (c) 1998-2002 The OpenSSL Project
d65 1
a65 1
             based ASCII-binary encoding which supports encryption with a
d100 1
a100 1
 rumored to exist. This is not a definitive list.
d110 2
a111 2
 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
d122 2
a123 9
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.

 PROBLEMS
 --------

 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.
d149 1
a149 2
 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/rt2.html) by mail to:
d153 1
a153 2
 Note that mail to openssl-bugs@@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
d167 1
a167 3
 if a TSA notification and a copy of the patch is sent to crypt@@bis.doc.gov;
 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
@


1.1.1.1.2.3.6.1
log
@MFC: OpenSSL 0.9.6e
@
text
@d2 1
a2 1
 OpenSSL 0.9.6e 30 July 2002
d4 1
a4 1
 Copyright (c) 1998-2002 The OpenSSL Project
d65 1
a65 1
             based ASCII-binary encoding which supports encryption with a
d100 1
a100 1
 rumored to exist. This is not a definitive list.
d110 2
a111 2
 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
d122 2
a123 9
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.

 PROBLEMS
 --------

 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.
d149 1
a149 2
 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/rt2.html) by mail to:
d153 1
a153 2
 Note that mail to openssl-bugs@@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
d167 1
a167 3
 if a TSA notification and a copy of the patch is sent to crypt@@bis.doc.gov;
 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
@


1.1.1.1.2.3.6.2
log
@Merge from RELENG_4_7: Update to OpenSSL 0.9.6i.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6i Feb 19 2003
d4 1
a4 1
 Copyright (c) 1998-2003 The OpenSSL Project
@


1.1.1.1.2.4
log
@MFC: OpenSSL 0.9.6e
@
text
@d2 1
a2 1
 OpenSSL 0.9.6e 30 July 2002
d4 1
a4 1
 Copyright (c) 1998-2002 The OpenSSL Project
d65 1
a65 1
             based ASCII-binary encoding which supports encryption with a
d100 1
a100 1
 rumored to exist. This is not a definitive list.
d110 2
a111 2
 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
d122 2
a123 9
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.

 PROBLEMS
 --------

 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.
d149 1
a149 2
 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/rt2.html) by mail to:
d153 1
a153 2
 Note that mail to openssl-bugs@@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
d167 1
a167 3
 if a TSA notification and a copy of the patch is sent to crypt@@bis.doc.gov;
 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
@


1.1.1.1.2.5
log
@MFC: OpenSSL 0.9.6g.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6g 9 August 2002
@


1.1.1.1.2.5.2.1
log
@Merge from RELENG_5_0: Update to OpenSSL 0.9.6i.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6i Feb 19 2003
d4 1
a4 1
 Copyright (c) 1998-2003 The OpenSSL Project
@


1.1.1.1.2.6
log
@MFC OpenSSL 0.9.7
@
text
@d2 1
a2 1
 OpenSSL 0.9.7 31 Dec 2002
d157 1
a157 1
 (http://www.openssl.org/support/rt2.html) by mail to:
@


1.1.1.1.2.7
log
@MFC OpenSSL 0.9.7a.

Approved by:	re (murray)
@
text
@d2 1
a2 1
 OpenSSL 0.9.7a Feb 19 2003
d4 1
a4 1
 Copyright (c) 1998-2003 The OpenSSL Project
@


1.1.1.1.2.8
log
@MFC OpenSSL 0.9.7c.

Approved by:	re
@
text
@d2 1
a2 1
 OpenSSL 0.9.7c 30 Sep 2003
@


1.1.1.1.2.9
log
@MFC OpenSSL 0.9.7d.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7d 17 Mar 2004
d4 1
a4 1
 Copyright (c) 1998-2004 The OpenSSL Project
@


1.1.1.2
log
@Initial import of OpenSSL 0.9.5a
@
text
@d2 1
a2 1
 OpenSSL 0.9.5a  1 Apr 2000
d4 1
a4 1
 Copyright (c) 1998-2000 The OpenSSL Project
d14 3
a16 4
 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. 
d83 1
a83 7
     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
d85 32
a159 2
    - Download the current snapshot from ftp://ftp.openssl.org/snapshot/
      to see if the problem has already been addressed
d162 2
d168 16
a183 9
    - 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)
a188 4
 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).

d194 3
a196 3
 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.
@


1.1.1.3
log
@Initial import of OpenSSL 0.9.6
@
text
@d2 1
a2 1
 OpenSSL 0.9.6 24 Sep 2000
d102 4
a105 3
 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/.
d107 2
a108 2
 RC4 is a trademark of RSA Security, so use of this label should perhaps
 only be used with RSA Security's permission. 
d122 3
a169 3
 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

d177 1
a177 1
 # diff -ur openssl-orig openssl-work > mydiffs.patch
@


1.1.1.4
log
@Initial import of OpenSSL 0.9.6a
@
text
@d2 1
a2 1
 OpenSSL 0.9.6a 5 Apr 2001
@


1.1.1.5
log
@Initial import of OpenSSL 0.9.6b
@
text
@d2 1
a2 1
 OpenSSL 0.9.6b  9 Jul 2001
d4 1
a4 1
 Copyright (c) 1998-2001 The OpenSSL Project
@


1.1.1.6
log
@Initial import of OpenSSL 0.9.6c
@
text
@d2 1
a2 1
 OpenSSL 0.9.6c 21 dec 2001
d65 1
a65 1
             based ASCII-binary encoding which supports encryption with a
d100 1
a100 1
 rumored to exist. This is not a definitive list.
d110 2
a111 2
 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
d122 2
a123 2
 lists the functions; you will probably have to look at the code to work out
 how to use them. Look at the example programs.
@


1.1.1.7
log
@Import of OpenSSL 0.9.6d.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6d 9 May 2002
d4 1
a4 1
 Copyright (c) 1998-2002 The OpenSSL Project
@


1.1.1.8
log
@Import of OpenSSL 0.9.6e.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6e 30 July 2002
a124 7
 PROBLEMS
 --------

 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.

d149 1
a149 2
 Report the bug to the OpenSSL project via the Request Tracker
 (http://www.openssl.org/rt2.html) by mail to:
d153 1
a153 2
 Note that mail to openssl-bugs@@openssl.org is recorded in the publicly
 readable request tracker database and is forwarded to a public
d167 1
a167 3
 if a TSA notification and a copy of the patch is sent to crypt@@bis.doc.gov;
 see http://www.bis.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html [sic]
 and http://w3.access.gpo.gov/bis/ear/pdf/740.pdf (EAR Section 740.13(e)).
@


1.1.1.9
log
@Import of OpenSSL 0.9.6f.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6f 8 August 2002
@


1.1.1.10
log
@Import of OpenSSL 0.9.6g.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6g 9 August 2002
@


1.1.1.10.2.1
log
@Update to OpenSSL 0.9.6i.
@
text
@d2 1
a2 1
 OpenSSL 0.9.6i Feb 19 2003
d4 1
a4 1
 Copyright (c) 1998-2003 The OpenSSL Project
@


1.1.1.11
log
@Vendor import of OpenSSL release 0.9.7. This release includes
support for AES and OpenBSD's hardware crypto.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7 31 Dec 2002
d157 1
a157 1
 (http://www.openssl.org/support/rt2.html) by mail to:
@


1.1.1.12
log
@Vendor import of OpenSSL 0.9.7a.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7a Feb 19 2003
d4 1
a4 1
 Copyright (c) 1998-2003 The OpenSSL Project
@


1.1.1.13
log
@Vendor import of OpenSSL 0.9.7c
@
text
@d2 1
a2 1
 OpenSSL 0.9.7c 30 Sep 2003
@


1.1.1.14
log
@Vendor import of OpenSSL 0.9.7d.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7d 17 Mar 2004
d4 1
a4 1
 Copyright (c) 1998-2004 The OpenSSL Project
@


1.1.1.14.2.1
log
@MFC update OpenSSL 0.9.7d -> 0.9.7e.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7e 25 Oct 2004
d176 3
a178 9
 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]
 and
    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.
d180 1
a180 1
 Our preferred format for changes is "diff -u" output. You might
@


1.1.1.15
log
@Vendor import of OpenSSL 0.9.7e.
@
text
@d2 1
a2 1
 OpenSSL 0.9.7e 25 Oct 2004
d176 3
a178 9
 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]
 and
    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.
d180 1
a180 1
 Our preferred format for changes is "diff -u" output. You might
@


1.1.1.16
log
@Vendor import of OpenSSL 0.9.8b
@
text
@d2 1
a2 1
 OpenSSL 0.9.8b 04 May 2006
d4 1
a4 1
 Copyright (c) 1998-2005 The OpenSSL Project
d17 1
a17 1
 related documentation.
d23 1
a23 1
 purposes as long as you fulfill the conditions of both licenses.
d56 1
a56 1
        RSA encryption/decryption/generation.
d58 1
a58 1
        DSA encryption/decryption/generation.
d60 1
a60 1
        Diffie-Hellman key-exchange/key generation.
d83 1
a83 1
 openssl:
d86 1
a86 1
        Creation of X.509 certificates, CSRs and CRLs
d92 1
a92 1

d107 1
a107 1
 only be used with RSA Security's permission.
a113 2
 The MDC2 algorithm is patented by IBM.

d132 1
a132 1
 SUPPORT
d141 1
a141 1
    - Remove compiler optimisation flags
a193 1

@


1.1.1.17
log
@Vendor import of OpenSSL 0.9.8d.
@
text
@d2 1
a2 1
 OpenSSL 0.9.8d 28 Sep 2006
d4 1
a4 1
 Copyright (c) 1998-2006 The OpenSSL Project
a115 4
 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

@


1.1.1.18
log
@Vendor import of OpenSSL 0.9.8e.
@
text
@d2 1
a2 1
 OpenSSL 0.9.8e 23 Feb 2007
d4 1
a4 1
 Copyright (c) 1998-2007 The OpenSSL Project
@


1.1.1.18.2.1
log
@SVN rev 215997 on 2010-11-28 13:45:51Z by simon

Merge OpenSSL 0.9.8p into stable/7.

This merges up to and including head/crypto/openssl/ r215697; and
head/secure/lib/libcrypto/, head/secure/lib/libssl/,
head/secure/usr.bin/openssl/ r215698.

To make the merge simpler, a hack was added to set MACHINE_CPUARCH.

A few old OpenSSL security fixes are still the stable/7 tree - these
will be backed out to the vendor version shortly.

Security:	CVE-2010-2939, CVE-2010-3864
Security:	http://www.openssl.org/news/secadv_20101116.txt
Security:	FreeBSD-SA-10:10.openssl
Approved by:	re (implicitly - they did not object of the general idea
		of OpenSSL update)
@
text
@d2 1
a2 1
 OpenSSL 0.9.8p 16 Nov 2010
d4 1
a4 1
 Copyright (c) 1998-2009 The OpenSSL Project
d39 6
a44 7
        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.
d114 2
a140 3
 See the OpenSSL website www.openssl.org for details of how to obtain
 commercial technical support.

d163 1
a163 1
 (http://www.openssl.org/support/rt.html) by mail to:
a166 4
 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.

d177 1
a177 1
 would like to submit a patch, send it to openssl-bugs@@openssl.org with
a180 12
 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 CVS 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
 features.

@


1.1.1.18.2.2
log
@SVN rev 216342 on 2010-12-09 22:05:16Z by simon

MFC r216166, r216167:

Merge in OpenSSL 0.9.8q.

Approved by:	re (kib)
Security:	CVE-2010-4180
Security:	http://www.openssl.org/news/secadv_20101202.txt
@
text
@d2 1
a2 1
 OpenSSL 0.9.8q 2 Dec 2010
@


1.1.1.18.2.3
log
@SVN rev 238001 on 2012-07-02 16:24:43Z by jkim

MFC:	r237657, r237658, r237666

Merge OpenSSL 0.9.8x and regen manual pages.
@
text
@d2 1
a2 1
 OpenSSL 0.9.8x 10 May 2012
d4 1
a4 1
 Copyright (c) 1998-2011 The OpenSSL Project
@


