|
| 1 | +THIRD PARTY LICENSE FILE |
| 2 | + |
| 3 | +Contents: |
| 4 | + |
| 5 | +A) SHA1 |
| 6 | +B) OpenSSL |
| 7 | +C) ACE(tm) |
| 8 | +D) LibTomCrypt |
| 9 | + |
| 10 | + |
| 11 | + |
| 12 | +***************************************************************************** |
| 13 | +A) The following software may be included in this product: RFC 3174 - US |
| 14 | +Secure Hash Algorithm 1 (SHA1). Use of any of this software is governed by |
| 15 | +terms of the license below: |
| 16 | +***************************************************************************** |
| 17 | + |
| 18 | +Full Copyright Statement |
| 19 | + |
| 20 | +Copyright (c) The Internet Society (2001). All Rights Reserved. |
| 21 | + |
| 22 | +This document and translations of it may be copied and furnished to others, |
| 23 | +and derivative works that comment on or otherwise explain it or assist in its |
| 24 | +implementation may be prepared, copied, published and distributed, in whole |
| 25 | +or in part, without restriction of any kind, provided that the above |
| 26 | +copyright notice and this paragraph are included on all such copies and |
| 27 | +derivative works. However, this document itself may not be modified in any |
| 28 | +way, such as by removing the copyright notice or references to the Internet |
| 29 | +Society or other Internet organizations, except as needed for the purpose of |
| 30 | +developing Internet standards in which case the procedures for copyrights |
| 31 | +defined in the Internet Standards process must be followed, or as required to |
| 32 | +translate it into languages other than English. |
| 33 | + |
| 34 | +The limited permissions granted above are perpetual and will not be revoked |
| 35 | +by the Internet Society or its successors or assigns. |
| 36 | + |
| 37 | +This document and the information contained herein is provided on an "AS IS" |
| 38 | +basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE |
| 39 | +DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO |
| 40 | +ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY |
| 41 | +RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A |
| 42 | +PARTICULAR PURPOSE. |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +***************************************************************************** |
| 47 | +B) The following software may be included in this product: OpenSSL. Use of |
| 48 | +any of this software is governed by terms of the license below: |
| 49 | +***************************************************************************** |
| 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 please |
| 55 | +contact openssl-core@openssl.org. |
| 56 | + |
| 57 | +OpenSSL License |
| 58 | +==================================================================== |
| 59 | +Copyright (c) 1998-2005 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 are met: |
| 63 | + |
| 64 | +1. Redistributions of source code must retain the above copyright notice, |
| 65 | +this list of conditions and the following disclaimer. |
| 66 | + |
| 67 | +2. Redistributions in binary form must reproduce the above copyright notice, |
| 68 | +this list of conditions and the following disclaimer in the documentation |
| 69 | +and/or other materials provided with the distribution. |
| 70 | + |
| 71 | +3. All advertising materials mentioning features or use of this software must |
| 72 | +display the following acknowledgment: "This product includes software |
| 73 | +developed by the OpenSSL Project for use in the OpenSSL Toolkit. |
| 74 | +(http://www.openssl.org/)" |
| 75 | + |
| 76 | +4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to |
| 77 | +endorse or promote products derived from this software without prior written |
| 78 | +permission. For written permission, please contact openssl-core@openssl.org. |
| 79 | + |
| 80 | +5. Products derived from this software may not be called "OpenSSL" nor may |
| 81 | +"OpenSSL" appear in their names without prior written permission of the |
| 82 | +OpenSSL Project. |
| 83 | + |
| 84 | +6. Redistributions of any form whatsoever must retain the following |
| 85 | +acknowledgment: "This product includes software developed by the OpenSSL |
| 86 | +Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" |
| 87 | + |
| 88 | +THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED |
| 89 | +OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES |
| 90 | +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN |
| 91 | +NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY |
| 92 | +DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES |
| 93 | +(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; |
| 94 | +LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND |
| 95 | +ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
| 96 | +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS |
| 97 | +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| 98 | +==================================================================== |
| 99 | + |
| 100 | +This product includes cryptographic software written by Eric Young |
| 101 | +(eay@cryptsoft.com). This product includes software written by Tim Hudson |
| 102 | +(tjh@cryptsoft.com). |
| 103 | + |
| 104 | + Original SSLeay License |
| 105 | + ----------------------- |
| 106 | + |
| 107 | +Copyright (c) 1995-1998 Eric Young (eay@cryptsoft.com) |
| 108 | +All rights reserved. |
| 109 | + |
| 110 | +This package is an SSL implementation written by Eric Young |
| 111 | +(eay@cryptsoft.com). The implementation was written so as to conform with |
| 112 | +Netscapes SSL. |
| 113 | + |
| 114 | +This library is free for commercial and non-commercial use as long as the |
| 115 | +following conditions are adhered to. The following conditions apply to all |
| 116 | +code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; |
| 117 | +not just the SSL code. The SSL documentation included with this distribution |
| 118 | +is covered by the same copyright terms except that the holder is Tim Hudson |
| 119 | +(tjh@cryptsoft.com). |
| 120 | + |
| 121 | +Copyright remains Eric Young's, and as such any Copyright notices in the code |
| 122 | +are not to be removed. If this package is used in a product, Eric Young |
| 123 | +should be given attribution as the author of the parts of the library used. |
| 124 | +This can be in the form of a textual message at program startup or in |
| 125 | +documentation (online or textual) provided with the package. |
| 126 | + |
| 127 | +Redistribution and use in source and binary forms, with or without |
| 128 | +modification, are permitted provided that the following conditions are met: |
| 129 | + |
| 130 | +1. Redistributions of source code must retain the copyright notice, this list |
| 131 | +of conditions and the following disclaimer. |
| 132 | + |
| 133 | +2. Redistributions in binary form must reproduce the above copyright notice, |
| 134 | +this list of conditions and the following disclaimer in the documentation |
| 135 | +and/or other materials provided with the distribution. |
| 136 | + |
| 137 | +3. All advertising materials mentioning features or use of this software must |
| 138 | +display the following acknowledgement: "This product includes cryptographic |
| 139 | +software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' |
| 140 | +can be left out if the routines from the library being used are not |
| 141 | +cryptographic related :-). |
| 142 | + |
| 143 | +4. If you include any Windows specific code (or a derivative thereof) from |
| 144 | +the apps directory (application code) you must include an acknowledgement: |
| 145 | +"This product includes software written by Tim Hudson (tjh@cryptsoft.com)" |
| 146 | + |
| 147 | +THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED |
| 148 | +WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
| 149 | +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO |
| 150 | +EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, |
| 151 | +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT |
| 152 | +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, |
| 153 | +OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF |
| 154 | +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING |
| 155 | +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, |
| 156 | +EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| 157 | + |
| 158 | +The license and distribution terms for any publicly available version or |
| 159 | +derivative of this code cannot be changed. i.e. this code cannot simply be |
| 160 | +copied and put under another distribution license [including the GNU Public |
| 161 | +License.] |
| 162 | + |
| 163 | + |
| 164 | + |
| 165 | +***************************************************************************** |
| 166 | +C) The following software may be included in this product: ACE(tm). Use of any |
| 167 | +of this software is governed by terms of the license below: |
| 168 | +***************************************************************************** |
| 169 | + |
| 170 | +Copyright and Licensing Information for ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM) |
| 171 | +ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM) (henceforth referred to as "DOC |
| 172 | +software") are copyrighted by Douglas C. Schmidt and his research group at |
| 173 | +Washington University, University of California, Irvine, and Vanderbilt |
| 174 | +University, Copyright (c) 1993-2005, all rights reserved. Since DOC software is |
| 175 | +open-source, freely available software, you are free to use, modify, copy, |
| 176 | +and distribute--perpetually and irrevocably--the DOC software source code and |
| 177 | +object code produced from the source, as well as copy and distribute modified |
| 178 | +versions of this software. You must, however, include this copyright |
| 179 | +statement along with code built using DOC software. |
| 180 | +You can use DOC software in commercial and/or binary software releases and |
| 181 | +are under no obligation to redistribute any of your source code that is built |
| 182 | +using DOC software. Note, however, that you may not do anything to the DOC |
| 183 | +software code, such as copyrighting it yourself or claiming authorship of the |
| 184 | +DOC software code, that will prevent DOC software from being distributed |
| 185 | +freely using an open-source development model. You needn't inform anyone that |
| 186 | +you're using DOC software in your software, though we encourage you to let us |
| 187 | +know so we can promote your project in the DOC software success stories. |
| 188 | +The ACE, TAO, CIAO, and CoSMIC web sites are maintained by the DOC Group at |
| 189 | +the Institute for Software Integrated Systems (ISIS) and the Center for |
| 190 | +Distributed Object Computing of Washington University, St. Louis for the |
| 191 | +development of open-source software as part of the open-source software |
| 192 | +community. By submitting comments, suggestions, code, code snippets, |
| 193 | +techniques (including that of usage) and algorithms (collectively |
| 194 | +``Submissions''), submitters acknowledge that they have the right to do so, |
| 195 | +that any such Submissions are given freely and unreservedly, and that they |
| 196 | +waive any claims to copyright or ownership. In addition, submitters |
| 197 | +acknowledge that any such Submission might become part of the copyright |
| 198 | +maintained on the overall body of code that comprises the DOC software. By |
| 199 | +making a Submission, submitter agrees to these terms. Moreover, submitters |
| 200 | +acknowledge that the incorporation or modification of such Submissions is |
| 201 | +entirely at the discretion of the moderators of the open-source DOC software |
| 202 | +projects or their designees. |
| 203 | +Submissions are provided by the submitter ``as is'' with no warranties |
| 204 | +whatsoever, including any warranty of merchantability, noninfringement of |
| 205 | +third party intellectual property, or fitness for any particular purpose. In |
| 206 | +no event shall the submitter be liable for any direct, indirect, special, |
| 207 | +exemplary, punitive, or consequential damages, including without limitation, |
| 208 | +lost profits, even if advised of the possibility of such damages. Likewise, |
| 209 | +DOC software is provided as is with no warranties of any kind, including the |
| 210 | +warranties of design, merchantability, and fitness for a particular purpose, |
| 211 | +noninfringement, or arising from a course of dealing, usage or trade |
| 212 | +practice. Washington University, UC Irvine, Vanderbilt University, their |
| 213 | +employees, and students shall have no liability with respect to the |
| 214 | +infringement of copyrights, trade secrets or any patents by DOC software or |
| 215 | +any part thereof. Moreover, in no event will Washington University, UC |
| 216 | +Irvine, or Vanderbilt University, their employees, or students be liable for |
| 217 | +any lost revenue or profits or other special, indirect and consequential |
| 218 | +damages. |
| 219 | +DOC software is provided with no support and without any obligation on the |
| 220 | +part of Washington University, UC Irvine, Vanderbilt University, their |
| 221 | +employees, or students to assist in its use, correction, modification, or |
| 222 | +enhancement. A number of companies around the world provide commercial |
| 223 | +support for DOC software, however. DOC software is Y2K-compliant, as long as |
| 224 | +the underlying OS platform is Y2K-compliant. |
| 225 | +The names ACE(TM), TAO(TM), CIAO(TM), CoSMIC(TM), Washington University, UC Irvine, |
| 226 | +and Vanderbilt University, may not be used to endorse or promote products or |
| 227 | +services derived from this source without express written permission from |
| 228 | +Washington University, UC Irvine, or Vanderbilt University. Further, products |
| 229 | +or services derived from this source may not be called ACE(TM), TAO(TM), CIAO(TM), |
| 230 | +or CoSMIC(TM) nor may the name Washington University, UC Irvine, or Vanderbilt |
| 231 | +University appear in their names, without express written permission from |
| 232 | +Washington University, UC Irvine, and Vanderbilt University. |
| 233 | + |
| 234 | + |
| 235 | + |
| 236 | +***************************************************************************** |
| 237 | +D) The following software may be included in this product: LibTomCrypt, |
| 238 | +Author: Tom St. Denis. Use of any of this software is licensed under |
| 239 | +PublicDomain. For more information, please visit http://libtomcrypt.org/. |
| 240 | +***************************************************************************** |
| 241 | + |
| 242 | +Copyright and Licensing Information for LibTomCrypt |
| 243 | +LibTomCrypt is a fairly comprehensive, modular and portable cryptographic |
| 244 | +toolkit that provides developers with a vast array of well known published |
| 245 | +block ciphers, one-way hash functions, chaining modes, pseudo-random number |
| 246 | +generators, public key cryptography and a plethora of other routines. |
| 247 | +LibTomCrypt has been designed from the ground up to be very simple to use. It |
| 248 | +has a modular and standard API that allows new ciphers, hashes and PRNGs to |
| 249 | +be added or removed without change to the overall end application. It |
| 250 | +features easy to use functions and a complete user manual which has many |
| 251 | +source snippet examples. |
| 252 | +LibTomCrypt is free for all purposes under the public domain. This includes |
| 253 | +commercial use, redistribution and even branching. |