• HOME

 

 

 

  "RfcAgiler" (hereinafter referred to as "this software") can only be used by those who agree to all of the following terms.
This software is the copyrighted work of the author of this software (the author) and is licensed only by the author.

(Establishment of contract)
Article 1
When the customer saves all or part of this software to a storage device such as a computer hard disk,
or uses this software, You are deemed to have agreed to the conclusion of this agreement,
and this agreement shall come into effect.

(Ownership of copyright)
Article 2.
All intellectual property rights such as copyrights related to this software belong to our company.

(Grant of usage rights)
Article 3
1. We grant you a non-exclusive right to use this software in accordance with the terms of this agreement.
2. You may install and use the Software on a hard disk or other storage device installed in your computer.

(Prohibited matter)
Article 4
1. You may not copy all or part of this software.
2. The customer may not license the use of this software to a third party, or sell, lend or lease this software to a third party.

(Disclaimer)
Article 5
1. We do not guarantee the operation, merchantability, suitability for a particular use, or any other aspect of this software to our customers.
2. We are not responsible for any direct or indirect damages suffered by you or any third party in relation to this software.
   The customer shall not be liable for any damages or losses related to claims made against the customer by a third party
   in connection with the use of this software.

(Termination of contract)
Article 6
1. The customer may terminate this agreement by erasing all of this software from storage devices
    such as hard disks and memory of the computer.
2. If the customer violates any provision of this agreement, our company can immediately terminate this agreement
    without any notice or demand to the customer.

(third party software)
Article 7
Online Storage Chat has acquired a patent license for file chat. Qt ((L)GPLv3) and OpenSSL(windows) described
in attachments 1 and 2 are included. Please read and understand the license conditions that apply to Attachments 1 and 2, respectively.

(Jurisdiction)
Article 8
This Agreement shall be governed by the laws of Japan.
Disputes relating to this Agreement shall be subject to the jurisdiction of the Tokyo District Court as the court of first instance.

that's all

Attachment 1
Qt ((L)GPLv3)
==================================
Developing with LGPL
These four degrees of freedom are very important for the success of the open-source Qt Project, and it is important that all users of Qt under
LGPL adhere to these and fully meet all the requirements set by the LGPL.
It is recommended that a thorough legal analysis is conducted when choosing to use any open-source licenses. In many cases, the LGPL is a
viable solution to use, but it is important that the freedoms of the LGPL are not restricted from the user of an application or device using an
LGPL library such as Qt, which may be difficult to achieve in some use cases.
For such cases the commercial licensing option is typically a better choice.The following requirements should be fulfilled when, for example,
creating an application or a device with Qt using the LGPL:

Complete corresponding source code of the library used with the application or the device built using LGPL, including all modifications to the
library, should be delivered with the application (or alternatively provide a written offer with instructions on how to get the source code). It
should be noted that the complete corresponding source code has to be delivered even if the library has not been modified at all.
In case of dynamic linking, it is possible, but not mandatory, to keep application source code proprietary as long as it is “work that uses the
library” ? typically achieved via dynamic linking of the library.
In case of static linking of the library, the application itself may no longer be “work that uses the library” and thus become subject to LGPL. It
is recommended to either link dynamically, or provide the application source code to the user under LGPL.
The user is allowed to change and re-link the library used in the application or device ? including reverse engineering. With LGPLv3 it is
explicitly stated that the user also needs to be able to run the re-linked binary, and that sufficient installation information must be provided. In
ractice, this forbids the creation of closed devices, also known as tivoization.
If the application or device is not fully following all requirements of the LGPL, it is not allowed to be distributed at all. This includes, for example,
possible patent license restricting distribution of the application in which case there is no right to distribute.
The freedoms provided by the LGPL license cannot be in any way negotiated upon or restricted from any of the recipients ? i.e. it is not
possible to make such terms for an application or a device using the LGPL library that would in any way restrict the rights provided by the
LGPL. For example some means of distribution, such as online application stores, may have rules that are in conflict with LGPL, in which case
those cannot be used with the LGPL licensing option of Qt.
The user of an application or device created with LGPL library has to be notified of their rights by providing a copy of the LGPL license text to
the user and displaying a prominent notice about using the LGPL library ? i.e. it is not allowed to hide the fact the LGPL library is used.
The LGPLv3 doesn’t forbid anyone from implementing any kind of DRM technology. However, if someone breaks the DRM, the license says that
he will be free to distribute his software. For more details, see the (L)GPLv3 license FAQ.
The LGPLv3 contains explicit patent clauses in order to prevent people from trying to enforce patent claims against other licensees of the
open source libraries. The clauses are rather complex but extremely relevant especially for larger corporations with software patents. So, it is
always recommended to go through the patent clauses carefully with a legal counsel to make sure this would not be an issue if deciding to use
LGPLv3. For more information and details, please see the (L)GPLv3 FAQ.

This is not a complete list of LGPL requirements ? please refer to the LGPL for complete list of requirements ? it is always recommended to
contact an experienced legal counsel to clarify detailed licensing suitability. Please note that The Qt Company does not offer legal guidance on
whether or not a certain license is suited for your need, or if your application or device meets the LGPL requirements. In case there is any
doubt whether or not the requirements of LGPL can be met in full, the commercial licensing option of Qt is often the best choice.


Attachment ２
OpenSSL
==================================
LiCENSE ISSUES

The OpenSSL toolkit stays under a dual 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. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to
OpenSSL please contact openssl-core@openssl.org.
OpenSSL License

Copyright (c) 1998-2005 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:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
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.

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/)"
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.

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.

Redistributions of any form whatsoever must retain the following acknowledgement:
"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 Netscape's SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to
all code found in this distribution, be it the RC4, RSA, hash, 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:

Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

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.

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 routines from the library being used are not cryptographic related.

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 license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be
copied and put under another distribution license (including the GNU Public License).