ReadMe.txt 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188
  1. THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION
  2. The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
  3. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
  4. - the Excluded Components are provided on an "AS IS" basis;
  5. - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE;
  6. - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components; and
  7. - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.
  8. ========================================================================
  9. This optional PKCS#11 component of ICC is derived from
  10. the RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki).
  11. The headers required to use this API are available from www.rsa.com.
  12. ========================================================================
  13. /* License to copy and use this software is granted provided that it is
  14. * identified as "RSA Security Inc. PKCS #11 Cryptographic Token Interface
  15. * (Cryptoki)" in all material mentioning or referencing this software.
  16. * License is also granted to make and use derivative works provided that
  17. * such works are identified as "derived from the RSA Security Inc. PKCS #11
  18. * Cryptographic Token Interface (Cryptoki)" in all material mentioning or
  19. * referencing the derived work.
  20. * RSA Security Inc. makes no representations concerning either the
  21. * merchantability of this software or the suitability of this software for
  22. * any particular purpose. It is provided "as is" without express or implied
  23. * warranty of any kind.
  24. */
  25. ========================================================================
  26. zlib: The program contains an embedded, statically linked copy of zlib. See www.zlib.net.
  27. A copy of the zlib license is appended below.
  28. ========================= Start zlib ====================================
  29. Copyright notice:
  30. (C) 1995-2004 Jean-loup Gailly and Mark Adler
  31. This software is provided 'as-is', without any express or implied
  32. warranty. In no event will the authors be held liable for any damages
  33. arising from the use of this software.
  34. Permission is granted to anyone to use this software for any purpose,
  35. including commercial applications, and to alter it and redistribute it
  36. freely, subject to the following restrictions:
  37. 1. The origin of this software must not be misrepresented; you must not
  38. claim that you wrote the original software. If you use this software
  39. in a product, an acknowledgment in the product documentation would be
  40. appreciated but is not required.
  41. 2. Altered source versions must be plainly marked as such, and must not be
  42. misrepresented as being the original software.
  43. 3. This notice may not be removed or altered from any source distribution.
  44. Jean-loup Gailly Mark Adler
  45. jloup@gzip.org madler@alumni.caltech.edu
  46. ============================== END zlib =================================
  47. OpenSSL: The Program is accompanied by software currently developed by The OpenSSL Project (http://www.openssl.org/). IBM obtained the majority of the OpenSSL software under the terms and conditions of the following licenses:
  48. ============================= Start OpenSSL =============================
  49. LICENSE ISSUES
  50. ==============
  51. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
  52. the OpenSSL License and the original SSLeay license apply to the toolkit.
  53. See below for the actual license texts. Actually both licenses are BSD-style
  54. Open Source licenses. In case of any license issues related to OpenSSL
  55. please contact openssl-core@openssl.org.
  56. OpenSSL License
  57. ---------------
  58. /* ====================================================================
  59. * Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
  60. *
  61. * Redistribution and use in source and binary forms, with or without
  62. * modification, are permitted provided that the following conditions
  63. * are met:
  64. *
  65. * 1. Redistributions of source code must retain the above copyright
  66. * notice, this list of conditions and the following disclaimer.
  67. *
  68. * 2. Redistributions in binary form must reproduce the above copyright
  69. * notice, this list of conditions and the following disclaimer in
  70. * the documentation and/or other materials provided with the
  71. * distribution.
  72. *
  73. * 3. All advertising materials mentioning features or use of this
  74. * software must display the following acknowledgment:
  75. * "This product includes software developed by the OpenSSL Project
  76. * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
  77. *
  78. * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
  79. * endorse or promote products derived from this software without
  80. * prior written permission. For written permission, please contact
  81. * openssl-core@openssl.org.
  82. *
  83. * 5. Products derived from this software may not be called "OpenSSL"
  84. * nor may "OpenSSL" appear in their names without prior written
  85. * permission of the OpenSSL Project.
  86. *
  87. * 6. Redistributions of any form whatsoever must retain the following
  88. * acknowledgment:
  89. * "This product includes software developed by the OpenSSL Project
  90. * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
  91. *
  92. * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
  93. * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  94. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  95. * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
  96. * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  97. * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  98. * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  99. * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  100. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
  101. * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  102. * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
  103. * OF THE POSSIBILITY OF SUCH DAMAGE.
  104. * ====================================================================
  105. *
  106. * This product includes cryptographic software written by Eric Young
  107. * (eay@cryptsoft.com). This product includes software written by Tim
  108. * Hudson (tjh@cryptsoft.com).
  109. *
  110. */
  111. Original SSLeay License
  112. -----------------------
  113. /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
  114. * All rights reserved.
  115. *
  116. * This package is an SSL implementation written
  117. * by Eric Young (eay@cryptsoft.com).
  118. * The implementation was written so as to conform with Netscapes SSL.
  119. *
  120. * This library is free for commercial and non-commercial use as long as
  121. * the following conditions are aheared to. The following conditions
  122. * apply to all code found in this distribution, be it the RC4, RSA,
  123. * lhash, DES, etc., code; not just the SSL code. The SSL documentation
  124. * included with this distribution is covered by the same copyright terms
  125. * except that the holder is Tim Hudson (tjh@cryptsoft.com).
  126. *
  127. * Copyright remains Eric Young's, and as such any Copyright notices in
  128. * the code are not to be removed.
  129. * If this package is used in a product, Eric Young should be given attribution
  130. * as the author of the parts of the library used.
  131. * This can be in the form of a textual message at program startup or
  132. * in documentation (online or textual) provided with the package.
  133. *
  134. * Redistribution and use in source and binary forms, with or without
  135. * modification, are permitted provided that the following conditions
  136. * are met:
  137. * 1. Redistributions of source code must retain the copyright
  138. * notice, this list of conditions and the following disclaimer.
  139. * 2. Redistributions in binary form must reproduce the above copyright
  140. * notice, this list of conditions and the following disclaimer in the
  141. * documentation and/or other materials provided with the distribution.
  142. * 3. All advertising materials mentioning features or use of this software
  143. * must display the following acknowledgement:
  144. * "This product includes cryptographic software written by
  145. * Eric Young (eay@cryptsoft.com)"
  146. * The word 'cryptographic' can be left out if the rouines from the library
  147. * being used are not cryptographic related :-).
  148. * 4. If you include any Windows specific code (or a derivative thereof) from
  149. * the apps directory (application code) you must include an acknowledgement:
  150. * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
  151. *
  152. * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
  153. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  154. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  155. * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
  156. * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  157. * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  158. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  159. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  160. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  161. * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  162. * SUCH DAMAGE.
  163. *
  164. * The licence and distribution terms for any publically available version or
  165. * derivative of this code cannot be changed. i.e. this code cannot simply be
  166. * copied and put under another distribution licence
  167. * [including the GNU Public Licence.]
  168. */