========================================================================

Apache Portable Runtime 1.5.2 License Agreement

========================================================================
The Apache Software Foundation uses various licenses to distribute software and
documentation, to accept regular contributions from individuals and corporations,
and to accept larger grants of existing software products.

These licenses help us achieve our goal of providing reliable and long-lived
software products through collaborative open source software development. In all
cases, contributors retain full rights to use their original contributions for any
other purpose outside of Apache while providing the ASF and its projects the right
to distribute and build upon their work within Apache.

Licensing of Distributions

All software produced by The Apache Software Foundation or any of its projects or
subjects is licensed according to the terms of the documents listed below.

Apache License, Version 2.0 (current)

http://www.apache.org/licenses/LICENSE-2.0 ( TXT or HTML )

The 2.0 version of the Apache License was approved by the ASF in 2004. The goals of
this license revision have been to reduce the number of frequently asked questions,
to allow the license to be reusable without modification by any project (including
non-ASF projects), to allow the license to be included by reference instead of
listed in every file, to clarify the license on submission of contributions, to
require a patent license on contributions that necessarily infringe the
contributor's own patents, and to move comments regarding Apache and other
inherited attribution notices to a location outside the license terms (the NOTICE
file ).

The result is a license that is supposed to be compatible with other open source
licenses, while remaining true to the original goals of the Apache Group and
supportive of collaborative development across both nonprofit and commercial
organizations. The Apache Software Foundation is still trying to determine if this
version of the Apache License is compatible with the GPL.

All packages produced by the ASF are implicitly licensed under the Apache License,
Version 2.0, unless otherwise explicitly stated. More developer documentation on
how to apply the Apache License to your work can be found in * Applying the Apache
License, Version 2.0 *.

Apache License, Version 1.1 (historic)

http://www.apache.org/licenses/LICENSE-1.1

The 1.1 version of the Apache License was approved by the ASF in 2000. The primary
change from the 1.0 license is in the 'advertising clause' (section 3 of the 1.0
license); derived products are no longer required to include attribution in their
advertising materials, only in their documentation.

Individual packages licensed under the 1.1 version may have used different wording
due to varying requirements for attribution or mark identification, but the binding
terms were all the same.

Apache License, Version 1.0 (historic)

http://www.apache.org/licenses/LICENSE-1.0
This is the original Apache License which applies only to older versions of Apache
packages (such as version 1.2 of the Web server).

Contributor License Agreements

The ASF desires that all contributors of ideas, code, or documentation to any
Apache projects complete, sign, and submit via email an Individual Contributor
License Agreement (ICLA).

The purpose of this agreement is to clearly define the terms under which
intellectual property has been contributed to the ASF and thereby allow us to
defend the project should there be a legal dispute regarding the software at some
future time. A signed ICLA is required to be on file before an individual is given
commit rights to any ASF project.

For a corporation that has assigned employees to work on an Apache project, a

Corporate CLA (CCLA) is available for contributing intellectual property via the
corporation, that may have been assigned as part of an employment agreement.

Note that a Corporate CLA does not remove the need for every developer to sign
their own ICLA as an individual, which covers both contributions which are owned
and those that are not owned by the corporation signing the CCLA.

The CCLA legally binds the corporation, so it must be signed by a person with
authority to enter into legal contracts on behalf of the corporation.

The ICLA is not tied to any employer you may have, so it is recommended to use
one's personal email address in the contact details, rather than an @work address.

Your Full name will be published unless you provide an alternative Public name. For
example if your full name is Andrew Bernard Charles Dickens, but you wish to be
known as Andrew Dickens, please enter the latter as your Public name.

The email address and other contact details are not published.

If you are submitting an ICLA in response to an invitation from a PMC, be sure to

identify the project via the form field "notify project". Also, choose a preferred
id that is not already in use. Apache ids must start with an alphabetic character
and contain at least two additional alphanumeric characters (no special
characters). You can check for ids in use here.

Software Grants

When an individual or corporation decides to donate a body of existing software or

documentation to one of the Apache projects, they need to execute a formal Software
Grant Agreement (SGA) with the ASF. Typically, this is done after negotiating
approval with the ASF Incubator or one of the PMCs, since the ASF will not accept
software unless there is a viable community available to support a collaborative
project.

Submitting License Agreements and Grants

Documents may be submitted by email and signed by hand or by electronic signature.

Postal mail hard copy and fax are no longer supported.

When submitting by email, please fill the form with a pdf viewer, then print, sign,
scan all pages into a single pdf file, and attach the pdf file to an email to
[email protected].
If possible, send the attachment from the email address in the document. Please
send only one document per email.

If you prefer to sign electronically, please fill the form, save it locally (e.g.
icla.pdf), and sign the file by preparing a detached PGP signature. For example,

gpg --armor --detach-sign icla.pdf

The above will create a file icla.pdf.asc. Send both the file (icla.pdf) and
signature (icla.pdf.asc) as attachments in the same email to [email protected].
Please send only one document (file plus signature) per email. Please do not submit
your public key to Apache. Instead, please upload your public key to
pgpkeys.mit.edu.

The files should be named icla.pdf and icla.pdf.asc for individual agreements;
ccla.pdf and ccla.pdf.asc for corporate agreements; software-grant.pdf and
software-grant.pdf.asc for grants.

We do not accept Zip files or other archives.

Please note that typing your name in the field at the bottom of the document is not
signing, regardless of the font that is used. Signing is either writing your
signature by hand on a printed copy of the document, or digitally signing via gpg.
Unsigned documents will not be accepted.

From wikipedia.org: A signature is a handwritten (and often stylized) depiction of

someone's name or nickname, on documents as a proof of identity and intent.

Provenance

Source code (including machine-readable documentation, release notes, guides, test

cases, run books, and scripts) in Apache repositories falls into three
classifications (solely for the purpose of this discussion):

Code developed at Apache under Apache governance, licensed to Apache by its

developers under a Contributor License Agreement, distributed by Apache, and
licensed to downstream users under the Apache license

This represents most code at Apache. The code contains a standard Apache license
header which refers to the standard Apache license in the distribution.

Code developed elsewhere, licensed to Apache under a Software Grant Agreement,

incorporated into Apache projects, distributed by Apache, and licensed to
downstream users under the Apache license

This is code that is being brought into Apache for future development as part of an
Apache project. The headers on all files are changed to the standard Apache header.
Most incubator projects start as externally-developed code and the Intellectual
Property Clearance process is done as part of incubation.

Code that is originally developed elsewhere and is being brought into Apache for
future development as part of an existing project must have the Intellectual
Property Clearance process done explicitly by the PMC of the receiving project,
under the auspices of the Incubator PMC which must approve the process.

Code developed elsewhere, received under a Category A license, incorporated into

Apache projects, distributed by Apache, and licensed to downstream users under its
original license

This code retains its external identity and is being incorporated into an Apache
project for convenience, to avoid referencing an external repository whose contents
are not under control of the project. The code retains its original license; and
distribution as part of the Apache project explicitly calls out the license. The
code retains its original header which refers to its own license in the
distribution. If changes are made to the code while at Apache, the standard Apache
header is prepended to each changed file. Additionally, any legally-required
notices related to the code are published in the distribution.

Export restrictions

For export restriction information, please consult our ASF Export Classifications
page.

Trademark and Logo Usage

For ASF trademark and logo usage information, please consult our ASF Trademark Use
Policy page.

Questions?

For answers to frequently asked licensing questions, please consult our Licensing
Frequently Asked Questions page.

========================================================================
Boost 1.70.0
========================================================================
Boost Software License - Version 1.0 - August 17th, 2003

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

obtaining a copy of the software and accompanying documentation covered by
this license (the "Software") to use, reproduce, display, distribute,
execute, and transmit the Software, and to prepare derivative works of the
Software, and to permit third-parties to whom the Software is furnished to
do so, all subject to the following:

The copyright notices in the Software and this entire statement, including
the above license grant, this restriction and the following disclaimer,
must be included in all copies of the Software, in whole or in part, and
all derivative works of the Software, unless such copies or derivative
works are solely in the form of machine-executable object code generated by
a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

========================================================================
Expat 2.2.5
========================================================================

Copyright (c) 1998-2000 Thai Open Source Software Center Ltd and Clark Cooper
Copyright (c) 2001-2017 Expat maintainers

Permission is hereby granted, free of charge, to any person obtaining a copy of

this software and associated documentation files (the "Software"), to deal in the
Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the
following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

========================================================================
ICU 4c64.2 License Agreement
========================================================================

UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE

NOTICE TO USER: Carefully read the following legal agreement.

BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S DATA FILES
("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), YOU UNEQUIVOCALLY ACCEPT, AND AGREE
TO BE BOUND BY, ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT
AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR
SOFTWARE.

COPYRIGHT AND PERMISSION NOTICE

Copyright � 1991-2019 Unicode, Inc. All rights reserved.
Distributed under the Terms of Use in https://www.unicode.org/copyright.html.

Permission is hereby granted, free of charge, to any person obtaining a copy of the
Unicode data files and any associated documentation (the "Data Files") or Unicode
software and any associated documentation (the "Software") to deal in the Data
Files or Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files
or Software, and to permit persons to whom the Data Files or Software are furnished
to do so, provided that either (a) this copyright and permission notice appear with
all copies of the Data Files or Software, or (b) this copyright and permission
notice appear in associated Documentation.
THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO
EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR
ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THE DATA FILES OR SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other dealings in
these Data Files or Software without prior written authorization of the copyright
holder.
========================================================================
Log4cxx License Agreement
========================================================================
Apache License - Version 2.0, January 2004

The Apache Software Foundation uses various licenses to distribute software and
documentation, to accept regular contributions from individuals and corporations,
and to accept larger grants of existing software products.

These licenses help us achieve our goal of providing reliable and long-lived
software products through collaborative open source software development. In all
cases, contributors retain full rights to use their original contributions for any
other purpose outside of Apache while providing the ASF and its projects the right
to distribute and build upon their work within Apache.

Licensing of Distributions

All software produced by The Apache Software Foundation or any of its projects or
subjects is licensed according to the terms of the documents listed below.

Apache License, Version 2.0 (current)

http://www.apache.org/licenses/LICENSE-2.0 ( TXT or HTML )

The 2.0 version of the Apache License was approved by the ASF in 2004. The goals of
this license revision have been to reduce the number of frequently asked questions,
to allow the license to be reusable without modification by any project (including
non-ASF projects), to allow the license to be included by reference instead of
listed in every file, to clarify the license on submission of contributions, to
require a patent license on contributions that necessarily infringe the
contributor's own patents, and to move comments regarding Apache and other
inherited attribution notices to a location outside the license terms (the NOTICE
file ).

The result is a license that is supposed to be compatible with other open source
licenses, while remaining true to the original goals of the Apache Group and
supportive of collaborative development across both nonprofit and commercial
organizations. The Apache Software Foundation is still trying to determine if this
version of the Apache License is compatible with the GPL.

All packages produced by the ASF are implicitly licensed under the Apache License,
Version 2.0, unless otherwise explicitly stated. More developer documentation on
how to apply the Apache License to your work can be found in * Applying the Apache
License, Version 2.0 *.

Apache License, Version 1.1 (historic)

http://www.apache.org/licenses/LICENSE-1.1

The 1.1 version of the Apache License was approved by the ASF in 2000. The primary
change from the 1.0 license is in the 'advertising clause' (section 3 of the 1.0
license); derived products are no longer required to include attribution in their
advertising materials, only in their documentation.

Individual packages licensed under the 1.1 version may have used different wording
due to varying requirements for attribution or mark identification, but the binding
terms were all the same.

Apache License, Version 1.0 (historic)

http://www.apache.org/licenses/LICENSE-1.0

This is the original Apache License which applies only to older versions of Apache
packages (such as version 1.2 of the Web server).

Contributor License Agreements

The ASF desires that all contributors of ideas, code, or documentation to any
Apache projects complete, sign, and submit via email an Individual Contributor
License Agreement (ICLA).

The purpose of this agreement is to clearly define the terms under which
intellectual property has been contributed to the ASF and thereby allow us to
defend the project should there be a legal dispute regarding the software at some
future time. A signed ICLA is required to be on file before an individual is given
commit rights to any ASF project.

For a corporation that has assigned employees to work on an Apache project, a

Corporate CLA (CCLA) is available for contributing intellectual property via the
corporation, that may have been assigned as part of an employment agreement.

Note that a Corporate CLA does not remove the need for every developer to sign
their own ICLA as an individual, which covers both contributions which are owned
and those that are not owned by the corporation signing the CCLA.

The CCLA legally binds the corporation, so it must be signed by a person with
authority to enter into legal contracts on behalf of the corporation.

The ICLA is not tied to any employer you may have, so it is recommended to use
one's personal email address in the contact details, rather than an @work address.

Your Full name will be published unless you provide an alternative Public name. For
example if your full name is Andrew Bernard Charles Dickens, but you wish to be
known as Andrew Dickens, please enter the latter as your Public name.

The email address and other contact details are not published.

If you are submitting an ICLA in response to an invitation from a PMC, be sure to

identify the project via the form field "notify project". Also, choose a preferred
id that is not already in use. Apache ids must start with an alphabetic character
and contain at least two additional alphanumeric characters (no special
characters). You can check for ids in use here.

Software Grants

When an individual or corporation decides to donate a body of existing software or

documentation to one of the Apache projects, they need to execute a formal Software
Grant Agreement (SGA) with the ASF. Typically, this is done after negotiating
approval with the ASF Incubator or one of the PMCs, since the ASF will not accept
software unless there is a viable community available to support a collaborative
project.

Submitting License Agreements and Grants

Documents may be submitted by email and signed by hand or by electronic signature.
Postal mail hard copy and fax are no longer supported.

When submitting by email, please fill the form with a pdf viewer, then print, sign,
scan all pages into a single pdf file, and attach the pdf file to an email to
[email protected].

If possible, send the attachment from the email address in the document. Please
send only one document per email.

If you prefer to sign electronically, please fill the form, save it locally (e.g.
icla.pdf), and sign the file by preparing a detached PGP signature. For example,
gpg --armor --detach-sign icla.pdf

The above will create a file icla.pdf.asc. Send both the file (icla.pdf) and
signature (icla.pdf.asc) as attachments in the same email to [email protected].
Please send only one document (file plus signature) per email. Please do not submit
your public key to Apache. Instead, please upload your public key to
pgpkeys.mit.edu.

The files should be named icla.pdf and icla.pdf.asc for individual agreements;
ccla.pdf and ccla.pdf.asc for corporate agreements; software-grant.pdf and
software-grant.pdf.asc for grants.

We do not accept Zip files or other archives.

Please note that typing your name in the field at the bottom of the document is not
signing, regardless of the font that is used. Signing is either writing your
signature by hand on a printed copy of the document, or digitally signing via gpg.
Unsigned documents will not be accepted.

From wikipedia.org: A signature is a handwritten (and often stylized) depiction of

someone's name or nickname, on documents as a proof of identity and intent.

Provenance

Source code (including machine-readable documentation, release notes, guides, test

cases, run books, and scripts) in Apache repositories falls into three
classifications (solely for the purpose of this discussion):

Code developed at Apache under Apache governance, licensed to Apache by its

developers under a Contributor License Agreement, distributed by Apache, and
licensed to downstream users under the Apache license

This represents most code at Apache. The code contains a standard Apache license
header which refers to the standard Apache license in the distribution.

Code developed elsewhere, licensed to Apache under a Software Grant Agreement,

incorporated into Apache projects, distributed by Apache, and licensed to
downstream users under the Apache license

This is code that is being brought into Apache for future development as part of an
Apache project. The headers on all files are changed to the standard Apache header.
Most incubator projects start as externally-developed code and the Intellectual
Property Clearance process is done as part of incubation.

Code that is originally developed elsewhere and is being brought into Apache for
future development as part of an existing project must have the Intellectual
Property Clearance process done explicitly by the PMC of the receiving project,
under the auspices of the Incubator PMC which must approve the process.

Code developed elsewhere, received under a Category A license, incorporated into

Apache projects, distributed by Apache, and licensed to downstream users under its
original license

This code retains its external identity and is being incorporated into an Apache
project for convenience, to avoid referencing an external repository whose contents
are not under control of the project. The code retains its original license; and
distribution as part of the Apache project explicitly calls out the license. The
code retains its original header which refers to its own license in the
distribution. If changes are made to the code while at Apache, the standard Apache
header is prepended to each changed file. Additionally, any legally-required
notices related to the code are published in the distribution.

Export restrictions

For export restriction information, please consult our ASF Export Classifications
page.

Trademark and Logo Usage

For ASF trademark and logo usage information, please consult our ASF Trademark Use
Policy page.

Questions?

For answers to frequently asked licensing questions, please consult our Licensing
Frequently Asked Questions page.

========================================================================
Minizip 1.2.6 License Agreement
========================================================================

Condition of use and distribution are the same as zlib:

2

3 This software is provided 'as-is', without any express or implied

4 warranty. In no event will the authors be held liable for any damages
5 arising from the use of this software.
6

7 Permission is granted to anyone to use this software for any purpose,

8 including commercial applications, and to alter it and redistribute it
9 freely, subject to the following restrictions:
10

11 1. The origin of this software must not be misrepresented; you must not
12 claim that you wrote the original software. If you use this software
13 in a product, an acknowledgement in the product documentation would be
14 appreciated but is not required.
15 2. Altered source versions must be plainly marked as such, and must not be
16 misrepresented as being the original software.
17 3. This notice may not be removed or altered from any source distribution.

========================================================================
OpenSSL 1.1.1n
========================================================================

LICENSE ISSUES
==============

The OpenSSL toolkit stays under a double license, i.e. both the conditions of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts.

OpenSSL License
---------------

/* ====================================================================
* Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* [email protected].
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software written by Eric Young
* ([email protected]). This product includes software written by Tim
* Hudson ([email protected]).
*
*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young ([email protected]).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson ([email protected]).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young ([email protected])"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson ([email protected])"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
*/

========================================================================
ActivePython 3.8.10
========================================================================

ActivePython 3.8.10 is used under an enterprise license with ActiveState.

========================================================================
zlib 1.2.8 License
========================================================================

/* zlib.h -- interface of the 'zlib' general purpose compression library

version 1.2.11, January 15th, 2017

Copyright (C) 1995-2017 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no

event will the authors be held liable for any damages arising from the use of this
software.
Permission is granted to anyone to use this software for any purpose, including
commercial applications, and to alter it and redistribute it freely, subject to the
following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that
you wrote the original software. If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is not
required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly [email protected]

Mark Adler [email protected]

========================================================================