LICENSE.txt 29 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603
  1. A. HISTORY OF THE SOFTWARE
  2. ==========================
  3. Python was created in the early 1990s by Guido van Rossum at Stichting
  4. Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
  5. as a successor of a language called ABC. Guido remains Python's
  6. principal author, although it includes many contributions from others.
  7. In 1995, Guido continued his work on Python at the Corporation for
  8. National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
  9. in Reston, Virginia where he released several versions of the
  10. software.
  11. In May 2000, Guido and the Python core development team moved to
  12. BeOpen.com to form the BeOpen PythonLabs team. In October of the same
  13. year, the PythonLabs team moved to Digital Creations, which became
  14. Zope Corporation. In 2001, the Python Software Foundation (PSF, see
  15. https://www.python.org/psf/) was formed, a non-profit organization
  16. created specifically to own Python-related Intellectual Property.
  17. Zope Corporation was a sponsoring member of the PSF.
  18. All Python releases are Open Source (see http://www.opensource.org for
  19. the Open Source Definition). Historically, most, but not all, Python
  20. releases have also been GPL-compatible; the table below summarizes
  21. the various releases.
  22. Release Derived Year Owner GPL-
  23. from compatible? (1)
  24. 0.9.0 thru 1.2 1991-1995 CWI yes
  25. 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes
  26. 1.6 1.5.2 2000 CNRI no
  27. 2.0 1.6 2000 BeOpen.com no
  28. 1.6.1 1.6 2001 CNRI yes (2)
  29. 2.1 2.0+1.6.1 2001 PSF no
  30. 2.0.1 2.0+1.6.1 2001 PSF yes
  31. 2.1.1 2.1+2.0.1 2001 PSF yes
  32. 2.1.2 2.1.1 2002 PSF yes
  33. 2.1.3 2.1.2 2002 PSF yes
  34. 2.2 and above 2.1.1 2001-now PSF yes
  35. Footnotes:
  36. (1) GPL-compatible doesn't mean that we're distributing Python under
  37. the GPL. All Python licenses, unlike the GPL, let you distribute
  38. a modified version without making your changes open source. The
  39. GPL-compatible licenses make it possible to combine Python with
  40. other software that is released under the GPL; the others don't.
  41. (2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
  42. because its license has a choice of law clause. According to
  43. CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
  44. is "not incompatible" with the GPL.
  45. Thanks to the many outside volunteers who have worked under Guido's
  46. direction to make these releases possible.
  47. B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
  48. ===============================================================
  49. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
  50. --------------------------------------------
  51. 1. This LICENSE AGREEMENT is between the Python Software Foundation
  52. ("PSF"), and the Individual or Organization ("Licensee") accessing and
  53. otherwise using this software ("Python") in source or binary form and
  54. its associated documentation.
  55. 2. Subject to the terms and conditions of this License Agreement, PSF hereby
  56. grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
  57. analyze, test, perform and/or display publicly, prepare derivative works,
  58. distribute, and otherwise use Python alone or in any derivative version,
  59. provided, however, that PSF's License Agreement and PSF's notice of copyright,
  60. i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
  61. 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation;
  62. All Rights Reserved" are retained in Python alone or in any derivative version
  63. prepared by Licensee.
  64. 3. In the event Licensee prepares a derivative work that is based on
  65. or incorporates Python or any part thereof, and wants to make
  66. the derivative work available to others as provided herein, then
  67. Licensee hereby agrees to include in any such work a brief summary of
  68. the changes made to Python.
  69. 4. PSF is making Python available to Licensee on an "AS IS"
  70. basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
  71. IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
  72. DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
  73. FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
  74. INFRINGE ANY THIRD PARTY RIGHTS.
  75. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
  76. FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
  77. A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
  78. OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
  79. 6. This License Agreement will automatically terminate upon a material
  80. breach of its terms and conditions.
  81. 7. Nothing in this License Agreement shall be deemed to create any
  82. relationship of agency, partnership, or joint venture between PSF and
  83. Licensee. This License Agreement does not grant permission to use PSF
  84. trademarks or trade name in a trademark sense to endorse or promote
  85. products or services of Licensee, or any third party.
  86. 8. By copying, installing or otherwise using Python, Licensee
  87. agrees to be bound by the terms and conditions of this License
  88. Agreement.
  89. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
  90. -------------------------------------------
  91. BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
  92. 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
  93. office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
  94. Individual or Organization ("Licensee") accessing and otherwise using
  95. this software in source or binary form and its associated
  96. documentation ("the Software").
  97. 2. Subject to the terms and conditions of this BeOpen Python License
  98. Agreement, BeOpen hereby grants Licensee a non-exclusive,
  99. royalty-free, world-wide license to reproduce, analyze, test, perform
  100. and/or display publicly, prepare derivative works, distribute, and
  101. otherwise use the Software alone or in any derivative version,
  102. provided, however, that the BeOpen Python License is retained in the
  103. Software, alone or in any derivative version prepared by Licensee.
  104. 3. BeOpen is making the Software available to Licensee on an "AS IS"
  105. basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
  106. IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
  107. DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
  108. FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
  109. INFRINGE ANY THIRD PARTY RIGHTS.
  110. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
  111. SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
  112. AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
  113. DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
  114. 5. This License Agreement will automatically terminate upon a material
  115. breach of its terms and conditions.
  116. 6. This License Agreement shall be governed by and interpreted in all
  117. respects by the law of the State of California, excluding conflict of
  118. law provisions. Nothing in this License Agreement shall be deemed to
  119. create any relationship of agency, partnership, or joint venture
  120. between BeOpen and Licensee. This License Agreement does not grant
  121. permission to use BeOpen trademarks or trade names in a trademark
  122. sense to endorse or promote products or services of Licensee, or any
  123. third party. As an exception, the "BeOpen Python" logos available at
  124. http://www.pythonlabs.com/logos.html may be used according to the
  125. permissions granted on that web page.
  126. 7. By copying, installing or otherwise using the software, Licensee
  127. agrees to be bound by the terms and conditions of this License
  128. Agreement.
  129. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
  130. ---------------------------------------
  131. 1. This LICENSE AGREEMENT is between the Corporation for National
  132. Research Initiatives, having an office at 1895 Preston White Drive,
  133. Reston, VA 20191 ("CNRI"), and the Individual or Organization
  134. ("Licensee") accessing and otherwise using Python 1.6.1 software in
  135. source or binary form and its associated documentation.
  136. 2. Subject to the terms and conditions of this License Agreement, CNRI
  137. hereby grants Licensee a nonexclusive, royalty-free, world-wide
  138. license to reproduce, analyze, test, perform and/or display publicly,
  139. prepare derivative works, distribute, and otherwise use Python 1.6.1
  140. alone or in any derivative version, provided, however, that CNRI's
  141. License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
  142. 1995-2001 Corporation for National Research Initiatives; All Rights
  143. Reserved" are retained in Python 1.6.1 alone or in any derivative
  144. version prepared by Licensee. Alternately, in lieu of CNRI's License
  145. Agreement, Licensee may substitute the following text (omitting the
  146. quotes): "Python 1.6.1 is made available subject to the terms and
  147. conditions in CNRI's License Agreement. This Agreement together with
  148. Python 1.6.1 may be located on the Internet using the following
  149. unique, persistent identifier (known as a handle): 1895.22/1013. This
  150. Agreement may also be obtained from a proxy server on the Internet
  151. using the following URL: http://hdl.handle.net/1895.22/1013".
  152. 3. In the event Licensee prepares a derivative work that is based on
  153. or incorporates Python 1.6.1 or any part thereof, and wants to make
  154. the derivative work available to others as provided herein, then
  155. Licensee hereby agrees to include in any such work a brief summary of
  156. the changes made to Python 1.6.1.
  157. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
  158. basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
  159. IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
  160. DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
  161. FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
  162. INFRINGE ANY THIRD PARTY RIGHTS.
  163. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
  164. 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
  165. A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
  166. OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
  167. 6. This License Agreement will automatically terminate upon a material
  168. breach of its terms and conditions.
  169. 7. This License Agreement shall be governed by the federal
  170. intellectual property law of the United States, including without
  171. limitation the federal copyright law, and, to the extent such
  172. U.S. federal law does not apply, by the law of the Commonwealth of
  173. Virginia, excluding Virginia's conflict of law provisions.
  174. Notwithstanding the foregoing, with regard to derivative works based
  175. on Python 1.6.1 that incorporate non-separable material that was
  176. previously distributed under the GNU General Public License (GPL), the
  177. law of the Commonwealth of Virginia shall govern this License
  178. Agreement only as to issues arising under or with respect to
  179. Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
  180. License Agreement shall be deemed to create any relationship of
  181. agency, partnership, or joint venture between CNRI and Licensee. This
  182. License Agreement does not grant permission to use CNRI trademarks or
  183. trade name in a trademark sense to endorse or promote products or
  184. services of Licensee, or any third party.
  185. 8. By clicking on the "ACCEPT" button where indicated, or by copying,
  186. installing or otherwise using Python 1.6.1, Licensee agrees to be
  187. bound by the terms and conditions of this License Agreement.
  188. ACCEPT
  189. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
  190. --------------------------------------------------
  191. Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
  192. The Netherlands. All rights reserved.
  193. Permission to use, copy, modify, and distribute this software and its
  194. documentation for any purpose and without fee is hereby granted,
  195. provided that the above copyright notice appear in all copies and that
  196. both that copyright notice and this permission notice appear in
  197. supporting documentation, and that the name of Stichting Mathematisch
  198. Centrum or CWI not be used in advertising or publicity pertaining to
  199. distribution of the software without specific, written prior
  200. permission.
  201. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
  202. THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
  203. FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
  204. FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
  205. WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
  206. ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
  207. OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  208. Additional Conditions for this Windows binary build
  209. ---------------------------------------------------
  210. This program is linked with and uses Microsoft Distributable Code,
  211. copyrighted by Microsoft Corporation. The Microsoft Distributable Code
  212. is embedded in each .exe, .dll and .pyd file as a result of running
  213. the code through a linker.
  214. If you further distribute programs that include the Microsoft
  215. Distributable Code, you must comply with the restrictions on
  216. distribution specified by Microsoft. In particular, you must require
  217. distributors and external end users to agree to terms that protect the
  218. Microsoft Distributable Code at least as much as Microsoft's own
  219. requirements for the Distributable Code. See Microsoft's documentation
  220. (included in its developer tools and on its website at microsoft.com)
  221. for specific details.
  222. Redistribution of the Windows binary build of the Python interpreter
  223. complies with this agreement, provided that you do not:
  224. - alter any copyright, trademark or patent notice in Microsoft's
  225. Distributable Code;
  226. - use Microsoft's trademarks in your programs' names or in a way that
  227. suggests your programs come from or are endorsed by Microsoft;
  228. - distribute Microsoft's Distributable Code to run on a platform other
  229. than Microsoft operating systems, run-time technologies or application
  230. platforms; or
  231. - include Microsoft Distributable Code in malicious, deceptive or
  232. unlawful programs.
  233. These restrictions apply only to the Microsoft Distributable Code as
  234. defined above, not to Python itself or any programs running on the
  235. Python interpreter. The redistribution of the Python interpreter and
  236. libraries is governed by the Python Software License included with this
  237. file, or by other licenses as marked.
  238. --------------------------------------------------------------------------
  239. This program, "bzip2", the associated library "libbzip2", and all
  240. documentation, are copyright (C) 1996-2010 Julian R Seward. All
  241. rights reserved.
  242. Redistribution and use in source and binary forms, with or without
  243. modification, are permitted provided that the following conditions
  244. are met:
  245. 1. Redistributions of source code must retain the above copyright
  246. notice, this list of conditions and the following disclaimer.
  247. 2. The origin of this software must not be misrepresented; you must
  248. not claim that you wrote the original software. If you use this
  249. software in a product, an acknowledgment in the product
  250. documentation would be appreciated but is not required.
  251. 3. Altered source versions must be plainly marked as such, and must
  252. not be misrepresented as being the original software.
  253. 4. The name of the author may not be used to endorse or promote
  254. products derived from this software without specific prior written
  255. permission.
  256. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
  257. OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
  258. WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  259. ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
  260. DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  261. DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
  262. GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
  263. INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
  264. WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
  265. NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
  266. SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  267. Julian Seward, jseward@bzip.org
  268. bzip2/libbzip2 version 1.0.6 of 6 September 2010
  269. --------------------------------------------------------------------------
  270. LICENSE ISSUES
  271. ==============
  272. The OpenSSL toolkit stays under a double license, i.e. both the conditions of
  273. the OpenSSL License and the original SSLeay license apply to the toolkit.
  274. See below for the actual license texts.
  275. OpenSSL License
  276. ---------------
  277. /* ====================================================================
  278. * Copyright (c) 1998-2018 The OpenSSL Project. All rights reserved.
  279. *
  280. * Redistribution and use in source and binary forms, with or without
  281. * modification, are permitted provided that the following conditions
  282. * are met:
  283. *
  284. * 1. Redistributions of source code must retain the above copyright
  285. * notice, this list of conditions and the following disclaimer.
  286. *
  287. * 2. Redistributions in binary form must reproduce the above copyright
  288. * notice, this list of conditions and the following disclaimer in
  289. * the documentation and/or other materials provided with the
  290. * distribution.
  291. *
  292. * 3. All advertising materials mentioning features or use of this
  293. * software must display the following acknowledgment:
  294. * "This product includes software developed by the OpenSSL Project
  295. * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
  296. *
  297. * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
  298. * endorse or promote products derived from this software without
  299. * prior written permission. For written permission, please contact
  300. * openssl-core@openssl.org.
  301. *
  302. * 5. Products derived from this software may not be called "OpenSSL"
  303. * nor may "OpenSSL" appear in their names without prior written
  304. * permission of the OpenSSL Project.
  305. *
  306. * 6. Redistributions of any form whatsoever must retain the following
  307. * acknowledgment:
  308. * "This product includes software developed by the OpenSSL Project
  309. * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
  310. *
  311. * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
  312. * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  313. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  314. * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
  315. * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  316. * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  317. * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  318. * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  319. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
  320. * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  321. * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
  322. * OF THE POSSIBILITY OF SUCH DAMAGE.
  323. * ====================================================================
  324. *
  325. * This product includes cryptographic software written by Eric Young
  326. * (eay@cryptsoft.com). This product includes software written by Tim
  327. * Hudson (tjh@cryptsoft.com).
  328. *
  329. */
  330. Original SSLeay License
  331. -----------------------
  332. /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
  333. * All rights reserved.
  334. *
  335. * This package is an SSL implementation written
  336. * by Eric Young (eay@cryptsoft.com).
  337. * The implementation was written so as to conform with Netscapes SSL.
  338. *
  339. * This library is free for commercial and non-commercial use as long as
  340. * the following conditions are aheared to. The following conditions
  341. * apply to all code found in this distribution, be it the RC4, RSA,
  342. * lhash, DES, etc., code; not just the SSL code. The SSL documentation
  343. * included with this distribution is covered by the same copyright terms
  344. * except that the holder is Tim Hudson (tjh@cryptsoft.com).
  345. *
  346. * Copyright remains Eric Young's, and as such any Copyright notices in
  347. * the code are not to be removed.
  348. * If this package is used in a product, Eric Young should be given attribution
  349. * as the author of the parts of the library used.
  350. * This can be in the form of a textual message at program startup or
  351. * in documentation (online or textual) provided with the package.
  352. *
  353. * Redistribution and use in source and binary forms, with or without
  354. * modification, are permitted provided that the following conditions
  355. * are met:
  356. * 1. Redistributions of source code must retain the copyright
  357. * notice, this list of conditions and the following disclaimer.
  358. * 2. Redistributions in binary form must reproduce the above copyright
  359. * notice, this list of conditions and the following disclaimer in the
  360. * documentation and/or other materials provided with the distribution.
  361. * 3. All advertising materials mentioning features or use of this software
  362. * must display the following acknowledgement:
  363. * "This product includes cryptographic software written by
  364. * Eric Young (eay@cryptsoft.com)"
  365. * The word 'cryptographic' can be left out if the rouines from the library
  366. * being used are not cryptographic related :-).
  367. * 4. If you include any Windows specific code (or a derivative thereof) from
  368. * the apps directory (application code) you must include an acknowledgement:
  369. * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
  370. *
  371. * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
  372. * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  373. * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  374. * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
  375. * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  376. * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  377. * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  378. * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  379. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  380. * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  381. * SUCH DAMAGE.
  382. *
  383. * The licence and distribution terms for any publically available version or
  384. * derivative of this code cannot be changed. i.e. this code cannot simply be
  385. * copied and put under another distribution licence
  386. * [including the GNU Public Licence.]
  387. */
  388. This software is copyrighted by the Regents of the University of
  389. California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
  390. Corporation and other parties. The following terms apply to all files
  391. associated with the software unless explicitly disclaimed in
  392. individual files.
  393. The authors hereby grant permission to use, copy, modify, distribute,
  394. and license this software and its documentation for any purpose, provided
  395. that existing copyright notices are retained in all copies and that this
  396. notice is included verbatim in any distributions. No written agreement,
  397. license, or royalty fee is required for any of the authorized uses.
  398. Modifications to this software may be copyrighted by their authors
  399. and need not follow the licensing terms described here, provided that
  400. the new terms are clearly indicated on the first page of each file where
  401. they apply.
  402. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
  403. FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
  404. ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
  405. DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
  406. POSSIBILITY OF SUCH DAMAGE.
  407. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
  408. INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
  409. FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
  410. IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
  411. NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
  412. MODIFICATIONS.
  413. GOVERNMENT USE: If you are acquiring this software on behalf of the
  414. U.S. government, the Government shall have only "Restricted Rights"
  415. in the software and related documentation as defined in the Federal
  416. Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
  417. are acquiring the software on behalf of the Department of Defense, the
  418. software shall be classified as "Commercial Computer Software" and the
  419. Government shall have only "Restricted Rights" as defined in Clause
  420. 252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
  421. authors grant the U.S. Government and others acting in its behalf
  422. permission to use and distribute the software in accordance with the
  423. terms specified in this license.
  424. This software is copyrighted by the Regents of the University of
  425. California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
  426. Corporation, Apple Inc. and other parties. The following terms apply to
  427. all files associated with the software unless explicitly disclaimed in
  428. individual files.
  429. The authors hereby grant permission to use, copy, modify, distribute,
  430. and license this software and its documentation for any purpose, provided
  431. that existing copyright notices are retained in all copies and that this
  432. notice is included verbatim in any distributions. No written agreement,
  433. license, or royalty fee is required for any of the authorized uses.
  434. Modifications to this software may be copyrighted by their authors
  435. and need not follow the licensing terms described here, provided that
  436. the new terms are clearly indicated on the first page of each file where
  437. they apply.
  438. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
  439. FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
  440. ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
  441. DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
  442. POSSIBILITY OF SUCH DAMAGE.
  443. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
  444. INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
  445. FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
  446. IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
  447. NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
  448. MODIFICATIONS.
  449. GOVERNMENT USE: If you are acquiring this software on behalf of the
  450. U.S. government, the Government shall have only "Restricted Rights"
  451. in the software and related documentation as defined in the Federal
  452. Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
  453. are acquiring the software on behalf of the Department of Defense, the
  454. software shall be classified as "Commercial Computer Software" and the
  455. Government shall have only "Restricted Rights" as defined in Clause
  456. 252.227-7013 (b) (3) of DFARs. Notwithstanding the foregoing, the
  457. authors grant the U.S. Government and others acting in its behalf
  458. permission to use and distribute the software in accordance with the
  459. terms specified in this license.
  460. Copyright (c) 1993-1999 Ioi Kim Lam.
  461. Copyright (c) 2000-2001 Tix Project Group.
  462. Copyright (c) 2004 ActiveState
  463. This software is copyrighted by the above entities
  464. and other parties. The following terms apply to all files associated
  465. with the software unless explicitly disclaimed in individual files.
  466. The authors hereby grant permission to use, copy, modify, distribute,
  467. and license this software and its documentation for any purpose, provided
  468. that existing copyright notices are retained in all copies and that this
  469. notice is included verbatim in any distributions. No written agreement,
  470. license, or royalty fee is required for any of the authorized uses.
  471. Modifications to this software may be copyrighted by their authors
  472. and need not follow the licensing terms described here, provided that
  473. the new terms are clearly indicated on the first page of each file where
  474. they apply.
  475. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
  476. FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
  477. ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
  478. DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
  479. POSSIBILITY OF SUCH DAMAGE.
  480. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
  481. INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
  482. FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
  483. IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
  484. NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
  485. MODIFICATIONS.
  486. GOVERNMENT USE: If you are acquiring this software on behalf of the
  487. U.S. government, the Government shall have only "Restricted Rights"
  488. in the software and related documentation as defined in the Federal
  489. Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
  490. are acquiring the software on behalf of the Department of Defense, the
  491. software shall be classified as "Commercial Computer Software" and the
  492. Government shall have only "Restricted Rights" as defined in Clause
  493. 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
  494. authors grant the U.S. Government and others acting in its behalf
  495. permission to use and distribute the software in accordance with the
  496. terms specified in this license.
  497. ----------------------------------------------------------------------
  498. Parts of this software are based on the Tcl/Tk software copyrighted by
  499. the Regents of the University of California, Sun Microsystems, Inc.,
  500. and other parties. The original license terms of the Tcl/Tk software
  501. distribution is included in the file docs/license.tcltk.
  502. Parts of this software are based on the HTML Library software
  503. copyrighted by Sun Microsystems, Inc. The original license terms of
  504. the HTML Library software distribution is included in the file
  505. docs/license.html_lib.