Red Hat Ansible License Agreement

The term “ansible” was coined in 1966 by Ursula K. The Guin in his novel Rocannon`s World[3] and refers to fictional instant communication systems. [4] [5] 1.2 Non-license. In addition, Red Hat grants the user, as a special waiver, the additional right to bind the RhDS code to code that is not covered by the GPL (“non-GPL Code”) and to distribute associated combinations, including both, subject to the restrictions in this paragraph. Non-GPL code allowed under this waiver can only be linked to the RHDS code through the well-defined interfaces specified in this file called EXCEPTION in the RHDS source files (“Trusted Interfaces”). Non-GPL Code files can initiate models or use macros or online functions from allowed interfaces, without the resulting work being covered by the GPL. Only Red Hat can make changes or additions to the list of approved interfaces. The user must comply with the GPL in all respects for all RHDS code and other codes used in combination with RHDS, with the exception of non-GPL code covered by this exception. If the user modifies RHDS, the user can extend this exception to their version of RHDS, but the user is not obliged to do so. If the user does not intend to provide this exception without modification, the user must remove this waiver statement from the user`s RHDS version and, without exception, license RHDS exclusively under the GPL license.

The purchase and use of Red Hat products and services is subject to an enterprise agreement, including an end user license agreement and the corresponding appendix(s) that contains exhibits for such Red Hat products and services. These agreements for different jurisdictions can be viewed by choosing a country below. This End User License Agreement (“EULA”) regulates the use of Red Hat Directory Server (which uses Administration Server and Red Hat Management Console) and Red Hat Certificate System (which uses enterprise Security Client and Auto Enrollment Proxy) and all associated updates to source code, appearance, structure, and organization (one “program” each), regardless of the deployment mechanism. 1.1 License Grant. Red Hat Directory Server (“RHDS”), Enterprise Security Client (“ESC”), and Auto Enrollment Proxy (“AEP”) are modular applications consisting of hundreds of software components and are collective works under U.S. copyright. Subject to the following conditions, Red Hat, Inc. (“Red Hat”) You (“Users”) have an unlimited worldwide license for RHDS, ESC and AEP, in accordance with the GNU General Public License v.2 (GPL).

Please note that the management server and red Hat Management Console, which are pure binary code used to configure and manage RHDS, are subject to the license terms in Section 2. The end user license agreement for each component of RHDS, ESC, and AEP can be found in the component`s source code. With the exception of certain image files listed in point 1.3 below, the license terms for the components allow the user to copy, modify and distribute the component as source and binary code. This AEE does not limit the user`s rights in the license terms of any particular component or grant them any rights of use that are at its side. 7. General. If any provision of this Agreement is held to be unenforceable, this shall not affect the enforceability of the remaining provisions. This Agreement is governed by the laws of the State of New York and the United States, without regard to conflict of laws rules. The rights and obligations of the Parties to this SEA are not subject to the United Nations Convention on the International Sale of Goods. . .