beautypg.com

38 english – Toshiba BDX5300 User Manual

Page 38

background image

38

English

ICU License - ICU 1.8.1 and later

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2011 International Business Machines

Corporation and others

All rights reserved.

Permission is hereby granted, free of charge, to any person

obtaining a copy of this software and associated documentation

files (the "Software"), to deal in the Software without restriction,

including without limitation the rights to use, copy, modify,

merge, publish, distribute, and/or sell copies of the Software,

and to permit persons to whom the Software is furnished to

do so, provided that the above copyright notice(s) and this

permission notice appear in all copies of the Software and that

both the above copyright notice(s) and this permission notice

appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY

OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT

LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS

FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF

THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT

HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE

LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR

CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER

RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER

IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER

TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION

WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright

holder shall not be used in advertising or otherwise to promote

the sale, use or other dealings in this Software without prior

written authorization of the copyright holder.

openssl

LICENSE ISSUES

The OpenSSL toolkit stays under a dual 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. Actually both licenses are BSD-style Open Source

licenses. In case of any license issues related to OpenSSL

please contact [email protected].

OpenSSL License

Copyright (c) 1998-2008 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 [email protected].

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 ([email protected]). This product includes software

written by Tim Hudson ([email protected]).

Original SSLeay License

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 adhered 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])"