beautypg.com

Sirius Satellite Radio 10 User Manual

Page 85

background image

[

EULA

]

the list of Contributing Authors: Cosmin Truta. libpng versions 1.0.7, July 1, 2000, through 1.2.5, October 3, 2002, are Copyright

(c) 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with

the following individuals added to the list of Contributing Authors: Simon-Pierre Cadieux, Eric S. Raymond, Gilles Vollant.libpng

versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright (c) 1998, 1999, 2000 Glenn Randers-Pehrson, and

are distributed according to the same disclaimer and license as libpng-0.96,with the following individuals added to the list of

Contributing Authors: Tom Lane, Glenn Randers-Pehrson, Willem van Schaik. libpng versions 0.89, June 1996, through 0.96, May

1997, are Copyright (c) 1996, 1997 Andreas Dilger Distributed according to the same disclaimer and license as libpng-0.88, with

the following individuals added to the list of Contributing Authors: John Bowler, Kevin Bracey, Sam Bushell, Magnus Holmgren,

Greg Roelofs, Tom Tanner. libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric

Schalnat, Group 42, Inc. For the purposes of this copyright and license, “Contributing Authors” is defined as the following set of in-

dividuals: Andreas Dilger, Dave Martindale, Guy Eric Schalnat, Paul Schmidt, Tim Wegner. The PNG Reference Library is supplied

“AS IS”. The Contributing Authors and Group 42, Inc. disclaim all warranties, expressed or implied, including, without limitation,

the warranties of merchantability and of fitness for any purpose. The Contributing Authors and Group 42, Inc. assume no liability

for direct, indirect, incidental, special, exemplary, or consequential damages, which may result from the use of the PNG Reference

Library, even if advised of the possibility of such damage. There is no warranty against interference with your enjoyment of the

library or against infringement. There is no warranty that our efforts or the library will fulfill any of your particular purposes or needs.

This library is provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with the user.

(i) openssl. Copyright (c) 1998-2005 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 WARRAN-

TIES, 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.

(j) SSLeay. Copyright (C) 1995-1998 Eric Young ([email protected]). All rights reserved. This package is an SSL implementation

written by Eric Young ([email protected]). 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 adheared 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 ([email protected]).

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 ([email protected])” The

word ‘cryptographic’ can be left out if the routines 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 include an acknowledgement:

“This product includes software written by Tim Hudson ([email protected])” 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 PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE