End User License Agreement(EULA)
As a user of shared atomic enterprise or any components involved, you have to accept the following terms:
The assumption of this software is that you should thoroughly read the this EULA, including supplement terms and terms in the external links, because they are all components of this EULA.
To accept the EULA or to use the software means you have agreed with all the terms. If you don't comply with these terms, you shouldn't use this software or any components included.

1) Software: Shared Atomic Enterprise
This EULA should be applied to any copy of Shared Atomic Enterprise software from any source, such as thorough internet, installed through any media, or any electronic device with Shared Atomic Enterprise ready to use when you get it.

2) Licensor:
Xiquan Ren,
Address:  No 95, Jingsiweiyi Rd, Shizhong district, Jinan, China

3) Licensee:
The user who is using the software.
The licensee becomes bound to the terms and conditions in the EULA upon download from internet, at opening any media such as CD, DVD, usb disk, or turn on any electronic device pre-installing this software.

5) Manual:
Contents on the website https://sharedatomic.top/

6) Device:
In this EULA, device is a kind of hardware system with internal storage, capable of running software, no matter physical hardware system or virtual hardware system. Hardware partition or blade computer should be treated as device.

4) Limitations of Warranties:
When the licensee received the software, is is being delivered "as is" and the licensor is not responsible for problems in maintaining the software integrity after delivery.
If the copy is downloaded from https://pypi.org/search/?q=shared_atomic_enterprise, the warrenties are limited to 1 year after the version is published.

5) Governing Law:
The execution of the agreement should be under the protection of the licensee's local law.

6) Infringement Acknowledgement:
Any kind of violation of this EULA should be avoided. If it has been determined that a user has used the software in a way that is against the EULA agreement, the licensor can revoke the license of the software from that user.

7) License Granting:
According to this EULA, we grant permission to install and upgrade this software and use this software as package of python after proper activation to one person at a time, the condition is the licensee agree to this EULA.
Licensee will need to use the serial number in the activation process to get the authorization. The activation process needs internet connection and a certain information transfer and cause service charge.
Upgrading nonproprietary version of this software won't make it proprietary. Under this condition, permission to use this software is still not granted to the licensee.

8) Limitations of Liability:
The licensor will not take any responsibility for any damages related to the use of the product except the compensations in section 17, even through the compensation didn't really meet its purpose. If the licensee's local law doesn't permit to disclaim this duty, this EULA does not fit the licensee's condition. If the licensee's local law can get the licensee compensation from the licensor, the compensation should be no more than the amount paid when the licensee buy this software licence.
The licensor does not provide any other claimed, unclaimed warranties or default warranties, if the licensee's local law does not permit to disclaim any warranties, the licensee can only get those warranties according to law. If the licensee's local law needs longer warranties, the warranties could be elongated accordingly, but the licensee can only get compensation permitted by section 17.

8) Maintenance and Support:
After-sales support will be provided to the licensee and it will be delivered by phone, according to our schedule on manual website.

9) Termination:
Infringement behavior or other illegal usage will result in immediate termination of the licence granted to licensee.

11) Use Restrictions:
The licensor keeps all other rights not mentioned in this EULA to himself. For example, this EULA doesn't grant the licensee the permission to and please don't
(i) copy, rent or lend the licence.
(ii) transfer the licence to other persons.
(iii) bypassing the technical limitations set by software.
(iv) setup any server to provide the usage of this software to other persons.
(v) reverse engineer, disassembly and decompile the software under any condition.
If licensee's local law permit these behaviors or these behaviors shouldn't be prohibited, this EULA does not fit the licensee's condition.

12) Multiple versions:
If licensee were provided multiple versions when purchasing the software, licensee can only install and activate one version a time.

13) Site Licenses:
This EULA only grants licensee the permission to install one copy on one device, no matter it is physical device or virtual device. If the licensee want to use this software under multiple virtual machines, please purchase separate licences.

14) Backup of the software:
Licensee can make a copy of the software for backup purpose.

15) Privacy policy:
This software may transfer the email address the licence bond to and randomly generated data to our activation server to keep the software activated.
The licencor will collect and use it to activate the software and track the licensee is the correct owner of the software licence.
The licencor will also use this email address to notify the licensee if this agreement changed.
We won't use and reveal this information for any other purpose.
Licensee should agree with this to use this software.

16) Upgrade:
The new version needs seperate licence by default, unless the licencor provided the free upgrade to the old version, and claim the old licence will work in new version.

17) Limitation of compensation:
If the licensor violated the limited warranty, the licensor would choose to:
(i) fix the software or replace the software for free.
(ii) refund and invalidate the licence.
(iii) give up the software.
This is the only compensation Licensee could get, unless there are other legal right according to Licensee's local law.

18) Return and refund:
If licensee buy the licence from other reseller, please contact them to get the refund. If licensee directly buy if from the licensor, please check When returning the licence, please check the manual.

19) Limitation of support:
The service agreement could be found at https://sharedatomic.top/enterprise_service.html

20) Complete term:
This EULA includs supplement terms and terms in the external links, because they are all components of this EULA.
After installation and activation, licensee could still read it by restart the activation process, and click "Read End User Licence Agreement" Button

21) Other authors:
The embedded cffi, whose author is Armin Rigo and Maciej Fijalkowski, as a dependency named _cffi_backend.cpython-39-x86_64-linux-gnu.so, is under following MIT licence.

    The MIT License

    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 embedded libffi, as a dependency named libffi.so, is under following liberal licence.

    libffi - Copyright (c) 1996-2022  Anthony Green, Red Hat, Inc and others.
    See source files for details.

    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 embedded python, which is a only under linux, as a dependency named libpython3.9.so.1.0, is under PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2.
the posix module in the dependency uses the OpenSSL library for added performance. The OpenSSL library is under the Openssl Licence
and Original SSLeay License which has been stated bellow.

    PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
    --------------------------------------------

    1. This LICENSE AGREEMENT is between the Python Software Foundation
    ("PSF"), and the Individual or Organization ("Licensee") accessing and
    otherwise using this software ("Python") in source or binary form and
    its associated documentation.

    2. Subject to the terms and conditions of this License Agreement, PSF hereby
    grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
    analyze, test, perform and/or display publicly, prepare derivative works,
    distribute, and otherwise use Python alone or in any derivative version,
    provided, however, that PSF's License Agreement and PSF's notice of copyright,
    i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
    2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 Python Software Foundation;
    All Rights Reserved" are retained in Python alone or in any derivative version
    prepared by Licensee.

    3. In the event Licensee prepares a derivative work that is based on
    or incorporates Python or any part thereof, and wants to make
    the derivative work available to others as provided herein, then
    Licensee hereby agrees to include in any such work a brief summary of
    the changes made to Python.

    4. PSF is making Python available to Licensee on an "AS IS"
    basis.  PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
    IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
    DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
    FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
    INFRINGE ANY THIRD PARTY RIGHTS.

    5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
    FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
    A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
    OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

    6. This License Agreement will automatically terminate upon a material
    breach of its terms and conditions.

    7. Nothing in this License Agreement shall be deemed to create any
    relationship of agency, partnership, or joint venture between PSF and
    Licensee.  This License Agreement does not grant permission to use PSF
    trademarks or trade name in a trademark sense to endorse or promote
    products or services of Licensee, or any third party.

    8. By copying, installing or otherwise using Python, Licensee
    agrees to be bound by the terms and conditions of this License
    Agreement.

    SipHash24 in libpython3.9.so.1.0
    Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note:
    <MIT License>
    Copyright (c) 2013  Marek Majkowski <marek@popcount.org>

    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.
    </MIT License>

    Original location:
       https://github.com/majek/csiphash/

    Solution inspired by code from:
       Samuel Neves (supercop/crypto_auth/siphash24/little)
       djb (supercop/crypto_auth/siphash24/little2)
       Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c)

    strtod and dtoa
    C functions dtoa and strtod for conversion of C doubles to and from strings,
    is derived from the file of the same name by David M. Gay, currently available
    from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c.
    The original file, as retrieved on March 16, 2009, contains the following copyright
    and licensing notice:
    /****************************************************************
     *
     * The author of this software is David M. Gay.
     *
     * Copyright (c) 1991, 2000, 2001 by Lucent Technologies.
     *
     * Permission to use, copy, modify, and distribute this software for any
     * purpose without fee is hereby granted, provided that this entire notice
     * is included in all copies of any software which is or includes a copy
     * or modification of this software and in all copies of the supporting
     * documentation for such software.
     *
     * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
     * WARRANTY.  IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY
     * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
     * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
     *
     ***************************************************************/


The embedded openssl, embedded in libdecryption11.so and libdecryption.so, is under following double licences.

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