1.2 License exception. In addition, as a special exception, Red Hat gives the user the additional right to link the HRSD code to a code that is not part of the GPL (“non-GPL code”) and to distribute related combinations, including both, subject to the limitations of this paragraph. The non-GPL code authorized under this exception can only be linked to the HRSD code through the well-defined interfaces identified in the file called EXCEPTION in source files for HRSD (the “approved interfaces”). Non-GPL code files can internalize models or use macros or online functions of authorized interfaces without the resulting work being covered by the GPL. Only Red Hat can make changes or additions to the list of authorized interfaces. The user must respect the GPL in all respects for all HRDS code and any other code used in association with HRSD, with the exception of the non-GPL code covered by this exception. If the user changes HRDS, the user can extend this exception to his version of HRSD, but the user is not obliged to do so. If the user does not wish to provide this exception without modification, the user must remove this exception statement from the USER`s version of HRSD without exception and use it under an HRDS license. 1.1 License grant. Red Hat Directory Server (“HRDS”), Enterprise Security Client (ESC) and Auto Enrollment Proxy (“AEP”) are modular applications, consisting of hundreds of software components and having collective works under U.S.
copyright. Subject to the following conditions, Red Hat, Inc. (“Red Hat”) grants you (“User”) an indeterminate global license for HRDS, ESC and AEP in accordance with the GNU v.2 General Public License (“LPG”). Please note that Administration Server and Red Hat Management Console, which are only binary codes for the configuration and management of HRSD, are subject to section 2 licensing conditions. The end-user license agreement for each component of HRSD, ESC and AEP is in the component`s source code. With the exception of some image files specified in section 1.3 below, the licensing conditions for components allow the user to copy, modify and redistribute the component into source and binary code forms. This Board does not limit the user`s rights to the licensing conditions of a particular component or grants successor user rights. 2.2 Changes to licensing. Red Hat intends to change the terms of the license granted pursuant to this Section 2 into an open source license. If such a change is generally announced to the public, the user has the option to submit RHCS, Admin Server and Console by the terms of such an open source license.
If the user does not make such a choice, the terms of this contract continue to apply to the user`s use of the RHCS, admin server and console. 7. Generalities. If a provision of this agreement is found to be unenforceable, it does not affect the applicability of the other provisions. This agreement is governed by the laws of the State of New York and the United States, regardless of the rules of conflict of laws. The rights and obligations of the parties to this ECJ are not governed by the UN Convention on the International Sale of Goods. 2.1 License grant. Subject to the provisions of this section 2.1, Red Hat grants the user a non-exclusive, non-negotiable, global, fully remunerated (without the right to sublicensing) for the use, reproduction and dissemination of the Red Hat Certificate (“RHCS”), Administration Server (“Admin Server”) and Red Hat Console (“Console”) in an executable and machine-readable form. The user must reproduce all ownership and ownership mentions on these copies. The user may reproduce rhcs, admin Server or Console and distribute it to another party only if the other party agrees in writing to be bound by the terms of this section 2.1. Except as provided in Section 2.1, the user cannot modify, copy, transfer or otherwise use RHCS, Admin Server or Console, and all licenses assigned to it are automatically terminated if the user does so.