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