[thirdparty/openssl.git] / README


 OpenSSL 1.1.0-pre3-dev

 Copyright (c) 1998-2016 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.WIN     Windows
        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.
Commit	Line	Data
d02b48c6	1
c60ebfdc	2	OpenSSL 1.1.0-pre3-dev
651d0aff	3
58add896	4	Copyright (c) 1998-2016 The OpenSSL Project
058bf559	5	Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
651d0aff RE	6	All rights reserved.
651d0aff RE	7
dfca822f RE	8	DESCRIPTION
	9	-----------
	10
f1c236f8	11	The OpenSSL Project is a collaborative effort to develop a robust,
651d0aff	12	commercial-grade, fully featured, and Open Source toolkit implementing the
b06935f4 RS	13	Secure Sockets Layer (SSLv3) and Transport Layer Security (TLS) protocols as
	14	well as a full-strength general purpose cryptograpic library. The project is
	15	managed by a worldwide community of volunteers that use the Internet to
	16	communicate, plan, and develop the OpenSSL toolkit and its related
	17	documentation.
651d0aff	18
b06935f4	19	OpenSSL is descended from the SSLeay library developed by Eric A. Young
1c308226	20	and Tim J. Hudson. The OpenSSL toolkit is licensed under a dual-license (the
b06935f4 RS	21	OpenSSL license plus the SSLeay license), which means that you are free to
	22	get and use it for commercial and non-commercial purposes as long as you
	23	fulfill the conditions of both licenses.
651d0aff	24
dfca822f RE	25	OVERVIEW
	26	--------
	27
1c308226	28	The OpenSSL toolkit includes:
651d0aff RE	29
651d0aff RE	30	libssl.a:
b06935f4	31	Provides the client and server-side implementations for SSLv3 and TLS.
651d0aff RE	32
651d0aff RE	33	libcrypto.a:
b06935f4 RS	34	Provides general cryptographic and X.509 support needed by SSL/TLS but
b06935f4 RS	35	not logically part of it.
651d0aff	36
a2c96d88	37	openssl:
d7f0ab5f	38	A command line tool that can be used for:
b06935f4	39	Creation of key parameters
a2c96d88	40	Creation of X.509 certificates, CSRs and CRLs
b06935f4 RS	41	Calculation of message digests
	42	Encryption and decryption
	43	SSL/TLS client and server tests
d7f0ab5f	44	Handling of S/MIME signed or encrypted mail
b06935f4	45	And more...
d7f0ab5f	46
dfca822f RE	47	INSTALLATION
	48	------------
	49
b06935f4 RS	50	See the appropriate file:
	51	INSTALL Linux, Unix, etc.
	52	INSTALL.DJGPP DOS platform with DJGPP
	53	INSTALL.NW Netware
	54	INSTALL.OS2 OS/2
	55	INSTALL.VMS VMS
7a77bd9d	56	INSTALL.WIN Windows
b06935f4	57	INSTALL.WCE Windows CE
80e1495b	58
a2c96d88	59	SUPPORT
dfca822f RE	60	-------
dfca822f RE	61
b06935f4	62	See the OpenSSL website www.openssl.org for details on how to obtain
0e37c909 DSH	63	commercial technical support.
0e37c909 DSH	64
dfca822f RE	65	If you have any problems with OpenSSL then please take the following steps
	66	first:
	67
d7f0ab5f UM	68	- Download the current snapshot from ftp://ftp.openssl.org/snapshot/
d7f0ab5f UM	69	to see if the problem has already been addressed
dfca822f	70	- Remove ASM versions of libraries
a2c96d88	71	- Remove compiler optimisation flags
dfca822f RE	72
	73	If you wish to report a bug then please include the following information in
	74	any bug report:
	75
d7f0ab5f UM	76	- On Unix systems:
	77	Self-test report generated by 'make report'
	78	- On other systems:
	79	OpenSSL version: output of 'openssl version -a'
	80	OS Name, Version, Hardware platform
	81	Compiler Details (name, version)
	82	- Application Details (name, version)
	83	- Problem Description (steps that will reproduce the problem, if known)
	84	- Stack Traceback (if the application dumps core)
dfca822f	85
468ab1c2	86	Email the report to:
dfca822f	87
932af161	88	rt@openssl.org
dfca822f	89
932af161 RS	90	In order to avoid spam, this is a moderated mailing list, and it might
932af161 RS	91	take a day for the ticket to show up. (We also scan posts to make sure
41977c53 RS	92	that security disclosures aren't publically posted by mistake.) Mail
	93	to this address is recorded in the public RT (request tracker) database
	94	(see https://www.openssl.org/community/index.html#bugs for details) and
	95	also forwarded the public openssl-dev mailing list. Confidential mail
	96	may be sent to openssl-security@openssl.org (PGP key available from the
	97	key servers).
0e37c909	98
932af161 RS	99	Please do NOT use this for general assistance or support queries.
	100	Just because something doesn't work the way you expect does not mean it
	101	is necessarily a bug in OpenSSL.
	102
	103	You can also make GitHub pull requests. If you do this, please also send
	104	mail to rt@openssl.org with a link to the PR so that we can more easily
	105	keep track of it.
a5ec86d1	106
b282fdae UM	107	HOW TO CONTRIBUTE TO OpenSSL
	108	----------------------------
	109
eb05f173	110	See CONTRIBUTING
b06935f4 RS	111
	112	LEGALITIES
	113	----------
	114
	115	A number of nations, in particular the U.S., restrict the use or export
	116	of cryptography. If you are potentially subject to such restrictions
	117	you should seek competent professional legal advice before attempting to
	118	develop or distribute cryptographic code.