Samsung LN32B650 User Manual

Also see for LN32B650: Manual Quick setup guide Safety instructions Quick setup guide User manual

Contents

LICENSE ISSUESThe OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay licenseapply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case ofany license issues related to OpenSSL please contact openssl-core@openssl.org.OpenSSL LicenseCopyright (c) 1998-2007 The OpenSSL Project. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditionsare 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 inthe documentation and/or other materials provided with the distribution.. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This productincludes 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 thissoftware without prior written permission. For written permission, please contact openssl-core@openssl.org.. Products derived from this software may not be called “OpenSSL nor may “OpenSSL” appear in their names without priorwritten permission of the OpenSSL Project.6. Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes software developedby 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 PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) 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 byTim 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 Eric Young (eay@cryptsoft.com). The implementation was written so as toconform with Netscapes SSL.This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The followingconditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSLdocumentation 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 ina 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 textualmessage 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 conditionsare 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 inthe documentation and/or other materials provided with the distribution.. All advertising materials mentioning features or use of this software must display the following acknowledgement: “Thisproduct includes cryptographic software written by Eric Young (eay@cryptsoft.com)” The word ‘cryptographic’ can be left out ifthe rouines from the library being used are not cryptographic related :-).4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must includean acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS’’ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) 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.The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this codecannot simply be copied and put under another distribution licence [including the GNU Public Licence.]¦