Users Guide
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY
AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE
COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO
MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation
of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect
according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil
liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return
for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible
use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under
these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to
most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where
the full notice is found.
ssleay32.dll
LICENSE ISSUES ============== The OpenSSL toolkit stays under a double license, i.e. both the conditions of the OpenSSL
License and the original SSLeay license apply to the toolkit. See below for the actual license texts. OpenSSL License
--------------- /* ==================================================================== * Copyright
(c) 1998-2017 The OpenSSL Project. All rights reserved. * * Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain
the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must
reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other
materials provided with the * distribution. * * 3. All advertising materials mentioning features or use of this * software must
display the following acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the
OpenSSL Toolkit. (http://www.openssl.org/)" * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without * prior written permission. For written permission, please
contact * openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" * nor may
"OpenSSL" appear in their names without prior written * permission of the OpenSSL Project. * * 6. Redistributions of any form
whatsoever must retain the following * acknowledgment: * "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)" * * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT
``AS IS'' AND ANY * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE OpenSSL PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF
SUCH DAMAGE. * ==================================================================== * * This
product includes cryptographic software written by Eric Young * (eay@cryptsoft.com). This product includes software written
by Tim * Hudson (tjh@cryptsoft.com). * */ Original SSLeay License ----------------------- /* Copyright (C) 1995-1998 Eric
Young (eay@cryptsoft.com) * All rights reserved. * * This package is an SSL implementation written * by Eric Young
(eay@cryptsoft.com). * The implementation was written so as to conform with Netscapes SSL. * * This library is free for
commercial and non-commercial use as long as * the following conditions are aheared to. The following conditions * apply to all
code found in this distribution, be it the RC4, RSA, * lhash, DES, etc., code; not just the SSL code. The SSL documentation *
included with this distribution is covered by the same copyright terms * except that the holder is Tim Hudson
(tjh@cryptsoft.com). * * Copyright remains Eric Young's, and as such any Copyright notices in * the code are not to be
removed. * If this package is used in a product, Eric Young should be given attribution * as the author of the parts of the library
used. * This can be in the form of a textual message at program startup or * in documentation (online or textual) provided with
the package. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that
the following conditions * are met: * 1. Redistributions of source code must retain the copyright * notice, this list of conditions
and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of
conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All
advertising materials mentioning features or use of this software * must display the following acknowledgement: * "This
product includes cryptographic software written by * Eric Young (eay@cryptsoft.com)" * The word 'cryptographic' can be left
36
Third party licenses