Panasonic AG-CPDIOCRUP Operating Instructions Manual

Contents

Panasonic AG-CPDIOCRUP Operating Instructions Manual Manual pdf 43 page image

43OpenSSL LicenseLICENSE ISSUESThe OpenSSL toolkit stays under a dual license, i.e. boththe conditions of the OpenSSL License and the originalSSLeay license apply to the toolkit.See below for the actual license texts. Actually bothlicenses are BSD-style Open Source licenses. In case ofany license issues related to OpenSSL please contactopenssl-core@openssl.org.OpenSSL LicenseCopyright (c) 1998-2002 The OpenSSL Project. All rightsreserved.Redistribution and use in source and binary forms, with orwithout modification, are permitted provided that thefollowing conditions are met:1. Redistributions of source code must retain the abovecopyright notice, this list of conditions and the followingdisclaimer.2. Redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materialsprovided with the distribution.3. All advertising materials mentioning features or use ofthis software must display the followingacknowledgment: “This product includes softwaredeveloped by the OpenSSL Project for use in theOpenSSL Toolkit. (http://www.openssl.org/)”4. The names “OpenSSL Toolkit” and “OpenSSL Project”must not be used to endorse or promote productsderived from this software without prior writtenpermission. For written permission, please contactopenssl-core@openssl.org.5. Products derived from this software may not be called“OpenSSL” nor may “OpenSSL” appear in their nameswithout prior written permission of the OpenSSL Project.6. Redistributions of any form whatsoever must retain thefollowing acknowledgment: “This product includessoftware developed by the OpenSSL Project for use inthe OpenSSL Toolkit (http://www.openssl.org/)”THIS SOFTWARE IS PROVIDED BY THE OpenSSLPROJECT “AS IS” AND ANY EXPRESSED OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.This product includes cryptographic software written byEric Young (eay@cryptsoft.com). This product includessoftware written by Tim Hudson (tjh@cryptsoft.com).Original SSLeay LicenseCopyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)All rights reserved.This package is an SSL implementation written by EricYoung (eay@cryptsoft.com).The implementation was written so as to conform withNetscapes SSL.This library is free for commercial and non-commercial useas long as the following conditions are aheared to. Thefollowing conditions apply to all code found in thisdistribution, be it the RC4, RSA, lhash, DES, etc., code;not just the SSL code. The SSL documentation includedwith this distribution is covered by the same copyrightterms except that the holder is Tim Hudson(tjh@cryptsoft.com).Copyright remains Eric Young’s, and as such anyCopyright notices in the code are not to be removed.If this package is used in a product, Eric Young should begiven attribution as the author of the parts of the libraryused.This can be in the form of a textual message at programstartup or in documentation (online or textual) providedwith the package.Redistribution and use in source and binary forms, with orwithout modification, are permitted provided that thefollowing conditions are met:1. Redistributions of source code must retain the copyrightnotice, this list of conditions and the followingdisclaimer.2. Redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materialsprovided with the distribution.3. All advertising materials mentioning features or use ofthis software must display the followingacknowledgement: “This product includes cryptographicsoftware written by Eric Young (eay@cryptsoft.com)”The word “cryptographic” can be left out if the rouinesfrom the library being used are not cryptographicrelated :-).4. If you include any Windows specific code (or aderivative thereof) from the apps directory (applicationcode) you must include an acknowledgement: “Thisproduct includes software written by Tim Hudson(tjh@cryptsoft.com)”THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “ASIS” AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. INNO EVENT SHALL THE AUTHOR OR CONTRIBUTORSBE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.The licence and distribution terms for any publicallyavailable version or derivative of this code cannot bechanged. i.e. this code cannot simply be copied and putunder another distribution licence [including the GNUPublic Licence.]