l   OpenSSL

l   Qt

l   SQLite

l   quazip

l   Cryptopp

 

 

l  OpenSSL

  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

 *    openssl-core@openssl.org.

 *

 * 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

 * (eay@cryptsoft.com).  This product includes software written by Tim

 * Hudson (tjh@cryptsoft.com).

 *

 */

 

 Original SSLeay License

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

 

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

 * All rights reserved.

 *

 * This package is an SSL implementation written

 * by Eric Young (eay@cryptsoft.com).

 * 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 (tjh@cryptsoft.com).

 *

 * 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 (eay@cryptsoft.com)"

 *    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 (tjh@cryptsoft.com)"

 *

 * 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.]

 */

 

 

l  Qt

GNU Lesser General Public License (LGPL)

Qt is available under the GNU Lesser General Public License version 3.

 

The Qt Toolkit is Copyright (C) 2018 The Qt Company Ltd. and other contributors.

Contact: https://www.qt.io/licensing/

 

Reference:

 

GNU Lesser General Public License, version 3

LGPL version 3

                   GNU LESSER GENERAL PUBLIC LICENSE

                       Version 3, 29 June 2007

 

 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>

 Everyone is permitted to copy and distribute verbatim copies

 of this license document, but changing it is not allowed.

 

  This version of the GNU Lesser General Public License incorporates

the terms and conditions of version 3 of the GNU General Public

License, supplemented by the additional permissions listed below.

 

  0. Additional Definitions.

 

  As used herein, "this License" refers to version 3 of the GNU Lesser

General Public License, and the "GNU GPL" refers to version 3 of the GNU

General Public License.

 

  "The Library" refers to a covered work governed by this License,

other than an Application or a Combined Work as defined below.

 

  An "Application" is any work that makes use of an interface provided

by the Library, but which is not otherwise based on the Library.

Defining a subclass of a class defined by the Library is deemed a mode

of using an interface provided by the Library.

 

  A "Combined Work" is a work produced by combining or linking an

Application with the Library.  The particular version of the Library

with which the Combined Work was made is also called the "Linked

Version".

 

  The "Minimal Corresponding Source" for a Combined Work means the

Corresponding Source for the Combined Work, excluding any source code

for portions of the Combined Work that, considered in isolation, are

based on the Application, and not on the Linked Version.

 

  The "Corresponding Application Code" for a Combined Work means the

object code and/or source code for the Application, including any data

and utility programs needed for reproducing the Combined Work from the

Application, but excluding the System Libraries of the Combined Work.

 

  1. Exception to Section 3 of the GNU GPL.

 

  You may convey a covered work under sections 3 and 4 of this License

without being bound by section 3 of the GNU GPL.

 

  2. Conveying Modified Versions.

 

  If you modify a copy of the Library, and, in your modifications, a

facility refers to a function or data to be supplied by an Application

that uses the facility (other than as an argument passed when the

facility is invoked), then you may convey a copy of the modified

version:

 

   a) under this License, provided that you make a good faith effort to

   ensure that, in the event an Application does not supply the

   function or data, the facility still operates, and performs

   whatever part of its purpose remains meaningful, or

 

   b) under the GNU GPL, with none of the additional permissions of

   this License applicable to that copy.

 

  3. Object Code Incorporating Material from Library Header Files.

 

  The object code form of an Application may incorporate material from

a header file that is part of the Library.  You may convey such object

code under terms of your choice, provided that, if the incorporated

material is not limited to numerical parameters, data structure

layouts and accessors, or small macros, inline functions and templates

(ten or fewer lines in length), you do both of the following:

 

   a) Give prominent notice with each copy of the object code that the

   Library is used in it and that the Library and its use are

   covered by this License.

 

   b) Accompany the object code with a copy of the GNU GPL and this license

   document.

 

  4. Combined Works.

 

  You may convey a Combined Work under terms of your choice that,

taken together, effectively do not restrict modification of the

portions of the Library contained in the Combined Work and reverse

engineering for debugging such modifications, if you also do each of

the following:

 

   a) Give prominent notice with each copy of the Combined Work that

   the Library is used in it and that the Library and its use are

   covered by this License.

 

   b) Accompany the Combined Work with a copy of the GNU GPL and this license

   document.

 

   c) For a Combined Work that displays copyright notices during

   execution, include the copyright notice for the Library among

   these notices, as well as a reference directing the user to the

   copies of the GNU GPL and this license document.

 

   d) Do one of the following:

 

       0) Convey the Minimal Corresponding Source under the terms of this

       License, and the Corresponding Application Code in a form

       suitable for, and under terms that permit, the user to

       recombine or relink the Application with a modified version of

       the Linked Version to produce a modified Combined Work, in the

       manner specified by section 6 of the GNU GPL for conveying

       Corresponding Source.

 

       1) Use a suitable shared library mechanism for linking with the

       Library.  A suitable mechanism is one that (a) uses at run time

       a copy of the Library already present on the user's computer

       system, and (b) will operate properly with a modified version

       of the Library that is interface-compatible with the Linked

       Version.

 

   e) Provide Installation Information, but only if you would otherwise

   be required to provide such information under section 6 of the

   GNU GPL, and only to the extent that such information is

   necessary to install and execute a modified version of the

   Combined Work produced by recombining or relinking the

   Application with a modified version of the Linked Version. (If

   you use option 4d0, the Installation Information must accompany

   the Minimal Corresponding Source and Corresponding Application

   Code. If you use option 4d1, you must provide the Installation

   Information in the manner specified by section 6 of the GNU GPL

   for conveying Corresponding Source.)

 

  5. Combined Libraries.

 

  You may place library facilities that are a work based on the

Library side by side in a single library together with other library

facilities that are not Applications and are not covered by this

License, and convey such a combined library under terms of your

choice, if you do both of the following:

 

   a) Accompany the combined library with a copy of the same work based

   on the Library, uncombined with any other library facilities,

   conveyed under the terms of this License.

 

   b) Give prominent notice with the combined library that part of it

   is a work based on the Library, and explaining where to find the

   accompanying uncombined form of the same work.

 

  6. Revised Versions of the GNU Lesser General Public License.

 

  The Free Software Foundation may publish revised and/or new versions

of the GNU Lesser General Public License from time to time. Such new

versions will be similar in spirit to the present version, but may

differ in detail to address new problems or concerns.

 

  Each version is given a distinguishing version number. If the

Library as you received it specifies that a certain numbered version

of the GNU Lesser General Public License "or any later version"

applies to it, you have the option of following the terms and

conditions either of that published version or of any later version

published by the Free Software Foundation. If the Library as you

received it does not specify a version number of the GNU Lesser

General Public License, you may choose any version of the GNU Lesser

General Public License ever published by the Free Software Foundation.

 

  If the Library as you received it specifies that a proxy can decide

whether future versions of the GNU Lesser General Public License shall

apply, that proxy's public statement of acceptance of any version is

permanent authorization for you to choose that version for the

Library.

 

 

l  SQLite

SQLite Is Public Domain

 

SQLite is in the

Public Domain

All of the code and documentation in SQLite has been dedicated to the public domain by

the authors. All code authors, and representatives of the companies they work for, have

signed affidavits dedicating their contributions to the public domain and originals of those

signed affidavits are stored in a firesafe at the main offices of Hwaci. Anyone is free to copy,

modify, publish, use, compile, sell, or distribute the original SQLite code, either in source

code form or as a compiled binary, for any purpose, commercial or non-commercial, and by

any means.

 

The previous paragraph applies to the deliverable code and documentation in SQLite –

those parts of the SQLite library that you actually bundle and ship with a larger application.

Some scripts used as part of the build process (for example the "configure" scripts

generated by autoconf) might fall under other open-source licenses. Nothing from these

build scripts ever reaches the final deliverable SQLite library, however, and so the licenses

associated with those scripts should not be a factor in assessing your rights to copy and use

the SQLite library.

 

All of the deliverable code in SQLite has been written from scratch. No code has been taken

from other projects or from the open internet. Every line of code can be traced back to its

original author, and all of those authors have public domain dedications on file. So the

SQLite code base is clean and is uncontaminated with licensed code from other projects.

 

Open-Source, not Open-Contribution

SQLite is open-source, meaning that you can make as many copies of it as you want and do

whatever you want with those copies, without limitation. But SQLite is not open-

contribution. In order to keep SQLite in the public domain and ensure that the code does

not become contaminated with proprietary or licensed content, the project does not accept

patches from unknown persons.

 

All of the code in SQLite is original, having been written specifically for use by SQLite. No

code has been copied from unknown sources on the internet.

 

Warranty of Title

SQLite is in the public domain and does not require a license. Even so, some organizations

want legal proof of their right to use SQLite. Circumstances where this occurs include the

following:

 

Your company desires indemnity against claims of copyright infringement.

You are using SQLite in a jurisdiction that does not recognize the public domain.

You are using SQLite in a jurisdiction that does not recognize the right of an author to

dedicate their work to the public domain.

You want to hold a tangible legal document as evidence that you have the legal right to use

and distribute SQLite.

Your legal department tells you that you have to purchase a license.

If any of the above circumstances apply to you, Hwaci, the company that employs all the

developers of SQLite, will sell you a Warranty of Title for SQLite. A Warranty of Title is a

legal document that asserts that the claimed authors of SQLite are the true authors, and

that the authors have the legal right to dedicate the SQLite to the public domain, and that

Hwaci will vigorously defend against challenges to those claims. All proceeds from the sale

of SQLite Warranties of Title are used to fund continuing improvement and support of

SQLite.

 

Contributed Code

In order to keep SQLite completely free and unencumbered by copyright, the project does

not accept patches. If you would like to make a suggested change, and include a patch as a

proof-of-concept, that would be great. However please do not be offended if we rewrite

your patch from scratch.   

 

      

l  quazip

Copyright (C) 2005-2020 Sergey A. Tachenov and contributors

Distributed under LGPL, full details in the COPYING file.

Original ZIP package is copyrighted by Gilles Vollant, see quazip/(un)zip.h files for details,

but basically it's the zlib license.

           

           

l  Cyptopp

Compilation Copyright (c) 1995-2010 by Wei Dai.  All rights reserved.

This copyright applies only to this software distribution package

as a compilation, and does not imply a copyright on any particular

file in the package.

 

All individual files in this compilation are placed in the public domain by

Wei Dai and other contributors.

 

I would like to thank the following authors for placing their works into

the public domain:

 

Joan Daemen - 3way.cpp

Leonard Janke - cast.cpp, seal.cpp

Steve Reid - cast.cpp

Phil Karn - des.cpp

Andrew M. Kuchling - md2.cpp, md4.cpp

Colin Plumb - md5.cpp

Seal Woods - rc6.cpp

Chris Morgan - rijndael.cpp

Paulo Baretto - rijndael.cpp, skipjack.cpp, square.cpp

Richard De Moliner - safer.cpp

Matthew Skala - twofish.cpp

Kevin Springle - camellia.cpp, shacal2.cpp, ttmac.cpp, whrlpool.cpp, ripemd.cpp

 

Permission to use, copy, modify, and distribute this compilation for

any purpose, including commercial applications, is hereby granted

without fee, subject to the following restrictions:

 

1. Any copy or modification of this compilation in any form, except

in object code form as part of an application software, must include

the above copyright notice and this license.

 

2. Users of this software agree that any modification or extension

they provide to Wei Dai will be considered public domain and not

copyrighted unless it includes an explicit copyright notice.

 

3. Wei Dai makes no warranty or representation that the operation of the

software in this compilation will be error-free, and Wei Dai is under no

obligation to provide any services, by way of maintenance, update, or

otherwise.  THE SOFTWARE AND ANY DOCUMENTATION ARE PROVIDED "AS IS"

WITHOUT EXPRESS OR IMPLIED WARRANTY INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE. IN NO EVENT WILL WEI DAI OR ANY OTHER CONTRIBUTOR BE LIABLE FOR

DIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

 

4. Users will not use Wei Dai or any other contributor's name in any

publicity or advertising, without prior written consent in each case.

 

5. Export of this software from the United States may require a

specific license from the United States Government.  It is the

responsibility of any person or organization contemplating export

to obtain such a license before exporting.

 

6. Certain parts of this software may be protected by patents.  It

is the users' responsibility to obtain the appropriate

licenses before using those parts.

 

If this compilation is used in object code form in an application

software, acknowledgement of the author is not required but would be

appreciated. The contribution of any useful modifications or extensions

to Wei Dai is not required but would also be appreciated.