71
June 2017 Third Party Notifications for the Open Text End User License Agreement Effective as of 1 June 2017

for the Open Text End User License Agreement...Shell, Secure Terminal, Secure Server, HostExplorer NFS Client and NFS Maestro Programs) SUPPLEMENTARY LICENSING CONDITIONS. The following

  • Upload
    others

  • View
    25

  • Download
    0

Embed Size (px)

Citation preview

  • June 2017

    Third Party Notificationsfor the Open Text End User License AgreementEffective as of 1 June 2017

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Table of Contents

    1. Connectivity Products (including: Exceed, Secure Shell, Secure Terminal,Secure Server, HostExplorer NFS Client and NFS Maestro Programs) ................. 3A. OpenText Exceed XDK ....................................................................................................................3B. OpenText Exceed 3D, OpenText Exceed XDK, or OpenText Exceed PowerSuite .........................3C. For OpenText Exceed, OpenText Exceed PowerSuite, OpenText Exceed onDemand,

    OpenText Exceed Freedom, OpenText HostExplorer, OpenText NFS Client, OpenTextSecure Shell, OpenText Secure Terminal or OpenText Secure Server...........................................4

    D. For OpenText Exceed, OpenText Exceed PowerSuite, OpenText HostExplorer,OpenText NFS Client, OpenText Secure Shell or OpenText Secure Terminal ...............................6

    E. For OpenText Exceed or OpenText Exceed PowerSuite.................................................................6F. For OpenText Exceed onDemand....................................................................................................7

    2. Output Management Products (including: Output Server (OS), OS WebDelivery, OS Distributor, OS Interface for SAP, OS International Printing,OS Explorer, OS Envoy, OS Manager and OS Smart Office Delivery).................. 12A. For Output Server ...........................................................................................................................12B. Output Server Web Delivery...........................................................................................................31C. Output Server Output Distributor ....................................................................................................32D. Output Server International Printing ...............................................................................................32

    3. OpenText Discovery Products (including: OpenText Axcelerate, OpenTextPerceptiv, and OpenText Decisiv product lines).................................................... 68

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 3

    1. Connectivity Products (including: Exceed, SecureShell, Secure Terminal, Secure Server, HostExplorerNFS Client and NFS Maestro Programs)

    SUPPLEMENTARY LICENSING CONDITIONS. The following supplementarylicensing conditions are hereby incorporated into and form part of this Agreement:

    A. OpenText Exceed XDKFor OpenText Exceed XDK the following supplemental licensing conditionsapply:

    Redistribution of OpenText Exceed XDK Components.

    Any application created with the components of the XDK may be distributed as longas it meets the following requirements:

    a) The following executables and help files may be distributed with an applicationcreated via the X Development Kit: LOCALCON.EXE and LOCALCON.HLP.b) The following executables and resource files may be distributed with an applicationcreated via the X Development Kit which uses the X Input Method: KINPUT2.EXE,SJ3SERV.EXE, KINPUT2, SERVERRC, SJ3MAIN.DIC, VISUAL.DIC, SJHK, SJRC,SJRK, SJSB, and SJZH.

    c) The following resource files may be distributed with an application created via the XDevelopment Kit: XERRORDB, XKEYSYMDB, LOCALE.DIR, LOCALE.ALIAS,COMPOSE.DIR, and all XLC_LOCALE files.

    d) The following dynamic link libraries (DLLs) may not be distributed with anyapplication created via the X Development Kit: XM.DLL, HCLMRM.DLL,HCLMRM12.DLL, HCLMRM21.DLL, HCLXM.DLL, HCLXM12.DLL andHCLXM21.DLL. All other DLL files included with the X Development Kit may bedistributed with an application without having to obtain a prior written agreement.

    e) The following static/import libraries may be linked with an application to bedistributed: XLIB.LIB, HCLXMU.LIB, HCLXT.LIB, HCLXAW.LIB, HCLICE.LIB,HCLSM.LIB, HCLXI.LIB, HCLXTST.LIB, HCLXM.LIB, HCLXIERT.LIB, HCLSHM.LIB,MRMSTAT.LIB, HCLUIL.LIB, XMSTATIC.LIB, XMSTATXT.LIB, HUMXPM.LIB, andHUMXRENDER.LIB. The above list is subject to change without notice.

    In order to distribute a derivative work or component of the XDK, which includesXM.DLL, HCLMRM.DLL, HCLMRM12.DLL, HCLMRM21.DLL, HCLXM.DLL,HCLXM12.DLL and HCLXM21.DLL, or requires a component not listed above,Licensee must first contact the Marketing Department at OPEN TEXT and obtain awritten agreement.

    B. OpenText Exceed 3D, OpenText Exceed XDK, or OpenText ExceedPowerSuite

    For OpenText Exceed 3D, OpenText Exceed XDK, or OpenText ExceedPowerSuite, the following supplemental licensing conditions apply:

    The contents of HCLGLX.DLL, HCLGLU.DLL, HCLGLUT.DLL, HCLAUX.DLL,HCLNURBS.DLL, LIBAUX.A, LIBGLU.A, LIBGLUT.A, LIBGLW.A, LIBGLX.A,LIBNURBS.A, GLWSTATI.LIB, HCLAUX.LIB, HCLGLU.LIB, HCLGLX.LIB,HCLGLUT.LIB and HCLNURBS.LIB are subject to Sections 2, 3, 4, 7, 8, 10, 12 and13 of the GLX Public License Version 1.0 (the "License"). Licensee may not use thesefiles except in compliance with those sections of the License. Licensee may obtain acopy of the License at Silicon Graphics, Inc., attn: Legal Services, 2011 N. ShorelineBlvd., Mountain View, CA 94043 or at:www.sgi.com/software/opensource/glx/license.html. Software distributed under the

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 4

    License is distributed on an "AS IS" basis. ALL WARRANTIES ARE DISCLAIMED,INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OFMERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE OR OFNONINFRINGEMENT. See the License for the specific language governing rights andlimitations under the License. The Original Software is GLX version 1.2 source code,released February, 1999. The developer of the Original Software is Silicon Graphics,Inc. Those portions of the Subject Software created by Silicon Graphics, Inc. areCopyright 1991-9 Silicon Graphics, Inc. All Rights Reserved.

    C. For OpenText Exceed, OpenText Exceed PowerSuite, OpenText ExceedonDemand, OpenText Exceed Freedom, OpenText HostExplorer,OpenText NFS Client, OpenText Secure Shell, OpenText Secure Terminalor OpenText Secure Server

    For OpenText Exceed, OpenText Exceed PowerSuite, OpenText ExceedonDemand, OpenText Exceed Freedom, OpenText HostExplorer, OpenText NFSClient, OpenText Secure Shell, OpenText Secure Terminal or OpenText SecureServer, the following supplemental licensing conditions apply:

    The contents of HUMSSLEAY32.DLL, HUMLIBEAY32.DLL, HUMSSLEAY32F.DLLand HUMLIBEAY32F.DLL are subject to OpenSSL License and the original SSLeayLicense:

    OpenSSL License

    Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, thislist 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 othermaterials provided with the distribution.3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgment: "This product includes software developed bythe OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used toendorse or promote products derived from this software without prior writtenpermission. For written permission, please contact [email protected]. Products derived from this software may not be called "OpenSSL" nor may"OpenSSL" appear in their names without prior written permission of the OpenSSLProject.6. Redistributions of any form whatsoever must retain the followingacknowledgment: "This product includes software developed by the OpenSSL Projectfor use in the OpenSSL Toolkit (http://www.openssl.org/)"

    THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODSOR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 5

    This product includes cryptographic software written by Eric Young([email protected]). This product includes software written by Tim Hudson([email protected]).

    Original SSLeay License

    Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.

    This package is an SSL implementation written by Eric Young ([email protected]).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 followingconditions are aheared to. The following conditions apply to all code found in thisdistribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. TheSSL documentation included with this distribution is covered by the same copyrightterms except that the holder is Tim Hudson ([email protected]).

    Copyright remains Eric Young's, and as such any Copyright notices in the code arenot to be removed.

    If this package is used in a product, Eric Young should be given attribution as theauthor of the parts of the library used. This can be in the form of a textual message atprogram startup or in documentation (online or textual) provided with the package.

    Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

    1. Redistributions of source code must retain the copyright notice, this list ofconditions 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 othermaterials provided with the distribution.3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgement: "This product includes cryptographic softwarewritten by Eric Young ([email protected])" The word 'cryptographic' can be left out ifthe routines from the library being used are not cryptographic related :-).4. If you include any Windows specific code (or a derivative thereof) from theapps directory (application code) you must include an acknowledgement: "Thisproduct includes software written by Tim Hudson ([email protected])"

    THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    The licence and distribution terms for any publically available version or derivative ofthis code cannot be changed. i.e. this code cannot simply be copied and put underanother distribution licence [including the GNU Public Licence.]

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 6

    D. For OpenText Exceed, OpenText Exceed PowerSuite, OpenTextHostExplorer, OpenText NFS Client, OpenText Secure Shell or OpenTextSecure Terminal

    For OpenText Exceed, OpenText Exceed PowerSuite, OpenText HostExplorer,OpenText NFS Client, OpenText Secure Shell or OpenText Secure Terminal, thefollowing supplemental licensing conditions apply:

    This software is being provided to you, the LICENSEE, by the Massachusetts Instituteof Technology (M.I.T) under the following license. By obtaining, using and/or copyingthis software, you agree that you have read, understood, and will comply with theseterms and conditions:

    Permission to use, copy, modify and distribute this software and its documentation forany purpose and without fee or royalty is hereby granted, provided that you agree tocomply with the following copyright notice and statements, including the disclaimer,and that the same appear on ALL copies of the software and documentation,including modifications that you make for internal use or for distribution:

    Copyright 1992-2005 by the Massachusetts Institute of Technology. All rightsreserved.

    THIS SOFTWARE IS PROVIDED "AS IS", AND M.I.T. MAKES NOREPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. By way ofexample, but not limitation, M.I.T. MAKES NO REPRESENTATIONS ORWARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULARPURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE ORDOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

    The name of the Massachusetts Institute of Technology or M.I.T. may NOT be used inadvertising or publicity pertaining to distribution of the software. Title to copyright inthis software and any associated documentation shall at all times remain with M.I.T.,and USER agrees to preserve same.

    Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos, Moira, OLC, XWindow System, and Zephyr are trademarks of the Massachusetts Institute ofTechnology (MIT). No commercial use of these trademarks may be made without priorwritten permission of MIT.

    E. For OpenText Exceed or OpenText Exceed PowerSuite

    For OpenText Exceed or OpenText Exceed PowerSuite, the followingsupplemental licensing conditions apply:

    Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, thislist 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 othermaterials provided with the distribution.3. The end-user documentation included with the redistribution, if any, mustinclude the following acknowledgment: "This product includes software developed bythe Apache Software Foundation (http://www.apache.org/)." Alternately, thisacknowledgment may appear in the software itself, if and wherever such third-partyacknowledgments normally appear.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 7

    4. The names "Xerces" and "Apache Software Foundation" must not be used toendorse or promote products derived from this software without prior writtenpermission. For written permission, please contact apache\@apache.org.5. Products derived from this software may not be called "Apache", nor may"Apache" appear in their name, without prior written permission of the ApacheSoftware Foundation.

    THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION ORITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    This software consists of voluntary contributions made by many individuals on behalfof the Apache Software Foundation, and was originally based on software copyright (c)1999, International Business Machines, Inc., http://www.ibm.com. For moreinformation on the Apache Software Foundation, please see.

    F. For OpenText Exceed onDemandFor OpenText Exceed onDemand, the following supplemental licensingconditions apply:

    OpenSSH license

    This file is part of the OpenSSH software.

    The licences which components of this software fall under are as follows. First, wewill summarize and say that all components are under a BSD licence, or a licencemore free than that.

    OpenSSH contains no GPL code.

    1) Copyright (c) 1995 Tatu Ylonen , Espoo, Finland. All rights reserved

    As far as I am concerned, the code I have written for this software can be used freelyfor any purpose. Any derived versions of this software must be clearly marked assuch, and if the derived work is incompatible with the protocol description in the RFCfile, it must be called by a name other than "ssh" or "Secure Shell".

    [Tatu continues]

    However, I am not implying to give any licenses to any patents or copyrights held bythird parties, and the software includes parts that are not under my direct control. Asfar as I know, all included source code is used in accordance with the relevant licenseagreements and can be used freely for any purpose (the GNU license being the mostrestrictive); see below for details.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 8

    [However, none of that term is relevant at this point in time. All of these restrictivelylicenced software components which he talks about have been removed fromOpenSSH, i.e.,

    RSA is no longer included, found in the OpenSSL library

    IDEA is no longer included, its use is deprecated

    DES is now external, in the OpenSSL library

    GMP is no longer used, and instead we call BN code from OpenSSL

    Zlib is now external, in a library

    The make-ssh-known-hosts script is no longer included

    TSS has been removed

    MD5 is now external, in the OpenSSL library

    RC4 support has been replaced with ARC4 support from OpenSSL

    Blowfish is now external, in the OpenSSL library

    [The licence continues]

    Note that any information and cryptographic algorithms used in this software arepublicly available on the Internet and at any major bookstore, scientific library, andpatent office worldwide. More information can be found e.g. at"http://www.cs.hut.fi/crypto".

    The legal status of this program is some combination of all these permissions andrestrictions. Use only at your own responsibility. You will be responsible for any legalconsequences yourself; I am not making any claims whether possessing or using thisis legal or not in your country, and I am not taking any responsibility on your behalf.

    NO WARRANTY

    BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NOWARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BYAPPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THECOPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "ASIS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THEENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM ISWITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THECOST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO INWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAYMODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BELIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE ORINABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OFDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BYYOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITHANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

    2) The 32-bit CRC compensation attack detector in deattack.c was contributed byCORE SDI S.A. under a BSD-style license.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 9

    Cryptographic attack detector for ssh - source code

    Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina. All rights reserved.Redistribution and use in source and binary forms, with or without modification, arepermitted provided that this copyright notice is retained.

    THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY ORCONSEQUENTIAL DAMAGES RESULTING FROM THE USE OR MISUSE OF THISSOFTWARE.

    Ariel Futoransky

    3) ssh-keyscan was contributed by David Mazieres under a BSD-style license.

    Copyright 1995, 1996 by David Mazieres .

    Modification and redistribution in source and binary forms is permitted provided thatdue credit is given to the author and the OpenBSD project by leaving this copyrightnotice intact.

    4) The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers and PauloBarreto is in the public domain and distributed with the following license:

    @version 3.0 (December 2000) Optimised ANSI C code for the Rijndael cipher (nowAES)

    @author Vincent Rijmen

    @author Antoon Bosselaers

    @author Paulo Barreto

    This code is hereby placed in the public domain.

    THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    5) One component of the ssh source code is under a 3-clause BSD license, held bythe University of California, since we pulled these parts from original Berkeley code.

    Copyright (c) 1983, 1990, 1992, 1993, 1995 The Regents of the University ofCalifornia. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 10

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

    2. Redistributions in binary form must reproduce the above copyright notice, this list ofconditions and the following disclaimer in the documentation and/or other materialsprovided with the distribution.

    3. Neither the name of the University nor the names of its contributors may The end-user documentation included with the redistribution, if any, must include the followingacknowledgment: "This product includes software developed by the Apache SoftwareFoundation (http://www.apache.org/)." Alternately, this acknowledgment may appearin the software itself, if and wherever such third-party acknowledgments normallyappear.

    The names "Xerces" and "Apache Software Foundation" must not be used to endorseor promote products derived from this software without specific prior writtenpermission.

    THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``ASIS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THEREGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODSOR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION)

    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    6) Remaining components of the software are provided under a standard 2-term BSDlicence with the following names as copyright holders:This software consists ofvoluntary contributions made by many individuals on behalf of the Apache SoftwareFoundation, and was originally based on software copyright (c) 1999, InternationalBusiness Machines, Inc., http://www.ibm.com . For more information on the ApacheSoftware Foundation, please see .

    Markus Friedl

    Theo de Raadt

    Niels Provos

    Dug Song

    Aaron Campbell

    Damien Miller

    Kevin Steves

    Daniel Kouril

    Wesley Griffin

    Per Allansson

    Nils Nordman

    Simon Wilkinson

    http://www.apache.org/)http://www.ibm.com/http://www.apache.org/

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 11

    Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

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

    2. Redistributions in binary form must reproduce the above copyright notice, this list ofconditions and the following disclaimer in the documentation and/or other materialsprovided with the distribution.

    THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL 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 ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

    ------

    $OpenBSD: LICENCE,v 1.19 2004/08/30 09:18:08 markus Exp $

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 12

    2. Output Management Products (including: OutputServer (OS), OS Web Delivery, OS Distributor, OSInterface for SAP, OS International Printing, OSExplorer, OS Envoy, OS Manager and OS SmartOffice Delivery)

    SUPPLEMENTARY LICENSING CONDITIONS. The following supplementary licensing conditions arehereby incorporated into and form part of this Agreement

    Output Server License InformationWeb Delivery License InformationOutput Distributor License InformationInternational Printing License Information

    A. For Output Server

    For Output Server following supplemental licensing conditions apply TopCopyright © 2016 Open Text. All Rights Reserved.Trademarks owned by Open Text.

    Portions of this software are:Copyright (c) 1983, 1990, 1996, 1998 Regents of the University of CaliforniaCopyright (c) 1987, 1988 Microsoft Systems JournalCopyright (c) 1987-1990 Massachusetts Institute of TechnologyCopyright (c) 1987, 1989 Student Information Processing Board of the

    Massachusetts Institute of TechnologyCopyright (c) 1987-2003 Larry Wall. All rights reserved.Copyright (c) 1988-1994 Aladdin Enterprises. Menlo Park, CaliforniaCopyright (c) 1988-1996 Sam LefflerCopyright (c) 1989, 1991, 1999 Free Software Foundation, Inc.Copyright (c) 1989, 1991-1992 Carnegie Mellon UniversityCopyright (c) 1990-1992 RSA Data Security, Inc.Copyright (c) 1991 Open Software Foundation, Inc.Copyright (c) 1990-1999 Microsoft CorporationCopyright (c) 1991 Digital Equipment CorporationCopyright (c) 1991 Hewlett-Packard CompanyCopyright (c) 1991-1996 Silicon Graphics, Inc.Copyright (c) 1992-1994 Atrium Technologies, Austin, TXCopyright (c) 1993, 1998 Soft Horizons. All rights reserved.Copyright (c) 1993 - 2005 SAP AG, WalldorfCopyright (c) 1995-1996 Neil WintonCopyright (c) 1995-1999 Citrix Systems Inc.Copyright (c) 1996, 1997 Dave RothCopyright (c) 1999, 2002 International Business Machines Corp.Copyright (c) 1996-1998 Monte MitzelfelCopyright (c) 1996-2001,2003 Aldo CalpinCopyright (c) 1997 Paul DiLasciaCopyright (c) 1997 Uwe HollerbachCopyright (c) 1997, 1998 Chris MaunderCopyright (c) 1997-2000 Gurusamy SarathyCopyright (c) 1997-2000 Jan DuboisCopyright (c) 1998 Christopher J. MadsenCopyright (c) 1998 Grahm BarrCopyright (c) 1998 Kirk Stowell

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 13

    Copyright (c) 1998, 2000, 2001 Bjorn Reese and Daniel Stenberg.Copyright (c) 1998-2000 Thai Open Source Software Center Ltd and Clark CooperCopyright (c) 1998-2001 Gisle AasCopyright (c) 1998-2001 Mike BlazerCopyright (c) 1999-2002 ActiveState CorpCopyright (c) 1998-2002 Daniel Veillard. All Rights Reserved.Copyright (c) 2000 Bjorn Reese and Daniel Veillard.Copyright (c) 2000 Gary Pennington and Daniel Veillard.Copyright (c) 2000-2004 Jason Hunter & Brett McLaughlin.Copyright (c) 2001, 2002 Expat maintainers.Copyright (C) 2015 Artifex Software, Inc. All rights reserved.Copyright (c) 2001-2003 E. I. DuPont de Nemours and Company, IncCopyright (c) 2001-2003 Lee GoddardCopyright (c) 2001,2003 Sean M. BurkeCopyright (c) 2003 Adam RichCopyright (c) 2003 Alexey ToptyginCopyright (c) 2003 James MacfarlaneCopyright (c) 2000-2006 MySQL AB & MySQL Finland AB & TCX DataKonsult ABCopyright (c) 2001-2002 Robin BerjonCopyright (c) 1998-2000 Larry Wall and Clark CooperCopyright (c) 2001 Matt SergeantCopyright (c) 1999-2003 Grant McLeanCopyright (c) 1999 Megginson TechnologiesCopyright (c) 2000 AxKit.com

    "This product includes software developed by the University of California,Berkeley and its contributors"

    Additional copyright and license information

    GhostScript:The files in the base, contrib, cups, doc, examples, iccprofiles,ijs, jbig2dec, lib, luratech/ldf_jb2, luratech/lwf_jp2, man, psi,Resource and toolbin directories (folders) and any subdirectories(sub-folders) are licensed as part of Artifex Ghostscript with theexception of the Resource/CMap directory (excluding the file"Identity-UTF16-H" which is copyright Artifex) which is licensedby Adobe allowing redistribution,

    The freetype, expat, icclib, imdi, jasper, jpeg, jpegxr, lcms, libpng,tiff, zlib and jpeg-xr directories are provided under separate licensecompatible with use with Artifex Ghostscript.

    This software is licensed to a single customer by Artifex Software Inc.under the terms of a specific OEM agreement.

    Among other things, the License requires that the copyright notice bepreserved on all files and this file must be included with all copies.

    Perl:Perl5 is Copyright (C) 1993-2005, by Larry Wall and others.It is free software; you can redistribute it and/or modify it under the terms of either:a) the GNU General Public License as published by the Free Software Foundation; either version 1, or(at your option) any later version , orb) the "Artistic License".

    OpenSSL:LICENSE ISSUES==============The OpenSSL toolkit stays under a dual license, i.e. both the conditions ofthe OpenSSL License and the original SSLeay license apply to the toolkit.See below for the actual license texts.

    OpenSSL License---------------

    http://dev.perl.org/licenses/gpl1.htmlhttp://www.fsf.org/http://dev.perl.org/licenses/gpl1.htmlhttp://www.fsf.org/licenses/licenses.htmlhttp://dev.perl.org/licenses/artistic.html

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 14

    /* ====================================================================* Copyright (c) 1998-2016 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* [email protected].** 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* ([email protected]). This product includes software written by Tim* Hudson ([email protected]).**/

    Original SSLeay License-----------------------

    /* Copyright (C) 1995-1998 Eric Young ([email protected])* All rights reserved.** This package is an SSL implementation written* by Eric Young ([email protected]).* 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

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 15

    * 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 ([email protected]).** 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 ([email protected])"* 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 ([email protected])"** 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.]*/

    Libssh2:/* Copyright (c) 2004-2007 Sara Golemon * Copyright (c) 2005,2006 Mikhail Gusarov * Copyright (c) 2006-2007 The Written Word, Inc.* Copyright (c) 2007 Eli Fant * Copyright (c) 2009-2014 Daniel Stenberg* Copyright (C) 2008, 2009 Simon Josefsson* 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

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 16

    * copyright notice, this list of conditions and the following* disclaimer in the documentation and/or other materials* provided with the distribution.** Neither the name of the copyright holder nor the names* of any other contributors may be used to endorse or* promote products derived from this software without* specific prior written permission.** THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND* CONTRIBUTORS "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 COPYRIGHT OWNER 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.*/

    LibTiff:Copyright (c) 1988-1997 Sam LefflerCopyright (c) 1991-1997 Silicon Graphics, Inc.

    Permission to use, copy, modify, distribute, and sell this software and its documentation for any purposeis hereby granted without fee, provided that (i) the above copyright notices and this permission noticeappear in all copies of the software and related documentation, and (ii) the names of Sam Leffler andSilicon Graphics may not be used in any advertising or publicity relating to the software without thespecific, prior written permission of Sam Leffler and Silicon Graphics.

    THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS,IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL,INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOTADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUTOF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE

    Enscript:This software package is covered under GNU General Public License Version 2. More about GeneralPublic License Version 2 can be found at http://www.gnu.org and is also stated as belowGNU General Public License Version 2

    Expect:This is free and unencumbered software released into the public domain.

    Anyone is free to copy, modify, publish, use, compile, sell, ordistribute this software, either in source code form or as a compiledbinary, for any purpose, commercial or non-commercial, and by anymeans.

    In jurisdictions that recognize copyright laws, the author or authorsof this software dedicate any and all copyright interest in thesoftware to the public domain. We make this dedication for the benefitof the public at large and to the detriment of our heirs andsuccessors. We intend this dedication to be an overt act ofrelinquishment in perpetuity of all present and future rights to this

    http://www.gnu.org/

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 17

    software under copyright law.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OROTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

    For more information, please refer to

    JBoss:LICENSE AGREEMENTJBOSS(r)

    This License Agreement governs the use of the Software Packages and any updates to the SoftwarePackages, regardless of the delivery mechanism. Each Software Package is a collective workunder U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants tothe user ("Client") a license to the applicable collective work(s) pursuant to theGNU Lesser General Public License v. 2.1 except for the following Software Packages:(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to theGNU General Public License v.2;

    (b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0;

    (c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensedunder the(open source) Sleepycat License (if Client does not wish to use the open source version of thisdatabase,it may purchase a license from Sleepycat Software);

    and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1,and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter variousroyalty-free patent licenses.

    Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php.

    1. The Software. "Software Packages" refer to the various software modules that are created andmade availablefor distribution by the JBoss.org open source community at http://www.jboss.org. Each of the SoftwarePackagesmay be comprised of hundreds of software components. The end user license agreement for eachcomponent is located inthe component's source code. With the exception of certain image files identified in Section 2 below,the license terms for the components permit Client to copy, modify, and redistribute the component,in both source code and binary code forms. This agreement does not limit Client's rights under,or grant Client rights that supersede, the license terms of any particular component.

    2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and areprotected under copyrightand other laws. Title to the Software Packages and any component, or to any copy, modification, ormerged portion shallremain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat"trademark, theindividual Software Package trademarks, and the "Shadowman" logo are registered trademarks of RedHat and its affiliatesin the U.S. and other countries. This agreement permits Client to distribute unmodified copies of theSoftware Packagesusing the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition thatClient follows Red Hat'strademark guidelines for those trademarks located athttp://www.redhat.com/about/corporate/trademark/. Client must abide bythese trademark guidelines when distributing the Software Packages, regardless of whether theSoftware Packages have been modified.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 18

    If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logosidentified athttp://www.jboss.com/company/logos unless a separate agreement with Red Hat is executed or otherpermission granted.Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages.

    3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particularcomponent, to the maximum extent permitted under applicable law, the Software Packages and thecomponents are provided and licensed "as is" without warranty of any kind, expressed or implied,including the implied warranties of merchantability, non-infringement or fitness for a particular purpose.Red Hat warrants that the media on which Software Packages may be furnished will be free fromdefects inmaterials and manufacture under normal use for a period of 30 days from the date of delivery to Client.Red Hat does not warrant that the functions contained in the Software Packages will meet Client'srequirementsor that the operation of the Software Packages will be entirely error free or appear precisely asdescribedin the accompanying documentation. This warranty extends only to the party that purchases theServicespertaining to the Software Packages from Red Hat or a Red Hat authorized distributor.

    4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, theremediesdescribed below are accepted by Client as its only remedies. Red Hat's entire liability, and Client'sexclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days ofdelivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it orrefund the money paid by Client for the Software. To the maximum extent permitted by applicable law,Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequentialdamages, including lost profits or lost savings arising out of the use or inability to use the Software,even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shallRed Hat's liability under this agreement exceed the amount that Client paid to Red Hat under thisAgreement during the twelve months preceding the action.

    5. Export Control. As required by U.S. law, Client represents and warrants that it:(a) understands that the Software Packages are subject to export controls under theU.S. Commerce Department's Export Administration Regulations ("EAR");

    (b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria);

    (c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity,or individual without the necessary export license(s) or authorizations(s) from the U.S. Government;

    (d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical orbiological weapons, or missile technology end-uses unless authorized by the U.S. Government byregulation or specific license;

    (e) understands and agrees that if it is in the United States and exports or transfers the SoftwarePackages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annualreports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name andaddress (including country) of each transferee;

    and (f) understands that countries other than the United States may restrict the import, use, orexport of encryption products and that it shall be solely responsible for compliance with any suchimport, use, or export restrictions.

    6. Third Party Programs. Red Hat may distribute third party software programs with the SoftwarePackagesthat are not part of the Software Packages and which Client must install separately. These third partyprograms are subject to their own license terms. The license terms either accompany the programs orcan be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicablelicense terms for such programs, then Client may not install them. If Client wishes to install theprogramson more than one system or transfer the programs to another party, then Client must contact thelicensorof the programs.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 19

    7. General. If any provision of this agreement is held to be unenforceable, that shall not affect theenforceability of the remaining provisions. This License Agreement shall be governed by the laws of theState of North Carolina and of the United States, without regard to any conflict of laws provisions,except that the United Nations Convention on the International Sale of Goods shall not apply.

    Copyright 2006-2007 Red Hat, Inc. All rights reserved."JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc.All other trademarks are the property of their respective owners.

    Yudit:This software package is covered under GNU General Public License Version 2. More about GeneralPublic License Version 2 can be found at http://www.gnu.org and is also stated as belowGNU General Public License Version 2

    Log4j:This software package is covered under Apache License Version 2.0. More about Apache LicenseVersion 2.0 can be found at http://www.apache.org/licenses and is also stated as belowApache License Version 2.0

    Myfaces:This software package is covered under Apache License Version 2.0. More about Apache LicenseVersion 2.0 can be found at http://www.apache.org/licenses and is also stated as belowApache License Version 2.0

    Tomahawk:This software package is covered under Apache License Version 2.0. More about Apache LicenseVersion 2.0 can be found at http://www.apache.org/licenses and is also stated as belowApache License Version 2.0

    Gmime:This software package is covered under GNU Lesser General Public License Version 2.1. More aboutLesser General Public License Version 2.1 can be found at http://www.gnu.org and is also stated asbelowGNU Lesser General Public License Version 2.1

    pkgconfig:This software package is covered under GNU General Public License Version 2. More about GeneralPublic License Version 2 can be found at http://www.gnu.org and is also stated as belowGNU General Public License Version 2

    glib:This software package is covered under GNU Library General Public License Version 2.1. More aboutLibrary General Public License Version 2.1 can be found at http://www.gnu.org and is also stated asbelowGNU Library General Public License Version 2.0

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

    Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the``Software''), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:

    The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

    http://www.gnu.org/

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 20

    CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

    Gettext:This software package is covered under GNU General Public License Version 3. More about GeneralPublic License Version 3 can be found at http://www.gnu.org and is also stated as belowGNU General Public License Version 3

    Pyhton:A. HISTORY OF THE SOFTWARE==========================

    Python was created in the early 1990s by Guido van Rossum at StichtingMathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlandsas a successor of a language called ABC. Guido remains Python'sprincipal author, although it includes many contributions from others.

    In 1995, Guido continued his work on Python at the Corporation forNational Research Initiatives (CNRI, see http://www.cnri.reston.va.us)in Reston, Virginia where he released several versions of thesoftware.

    In May 2000, Guido and the Python core development team moved toBeOpen.com to form the BeOpen PythonLabs team. In October of the sameyear, the PythonLabs team moved to Digital Creations (now ZopeCorporation, see http://www.zope.com). In 2001, the Python SoftwareFoundation (PSF, see http://www.python.org/psf/) was formed, anon-profit organization created specifically to own Python-relatedIntellectual Property. Zope Corporation is a sponsoring member ofthe PSF.

    All Python releases are Open Source (see http://www.opensource.org forthe Open Source Definition). Historically, most, but not all, Pythonreleases have also been GPL-compatible; the table below summarizesthe various releases.

    Release Derived Year Owner GPL-from compatible? (1)

    0.9.0 thru 1.2 1991-1995 CWI yes1.3 thru 1.5.2 1.2 1995-1999 CNRI yes1.6 1.5.2 2000 CNRI no2.0 1.6 2000 BeOpen.com no1.6.1 1.6 2001 CNRI yes (2)2.1 2.0+1.6.1 2001 PSF no2.0.1 2.0+1.6.1 2001 PSF yes2.1.1 2.1+2.0.1 2001 PSF yes2.2 2.1.1 2001 PSF yes2.1.2 2.1.1 2002 PSF yes2.1.3 2.1.2 2002 PSF yes2.2.1 2.2 2002 PSF yes2.2.2 2.2.1 2002 PSF yes2.2.3 2.2.2 2003 PSF yes2.3 2.2.2 2002-2003 PSF yes2.3.1 2.3 2002-2003 PSF yes2.3.2 2.3.1 2002-2003 PSF yes2.3.3 2.3.2 2002-2003 PSF yes2.3.4 2.3.3 2004 PSF yes2.3.5 2.3.4 2005 PSF yes2.4 2.3 2004 PSF yes2.4.1 2.4 2005 PSF yes2.4.2 2.4.1 2005 PSF yes2.4.3 2.4.2 2006 PSF yes2.4.4 2.4.3 2006 PSF yes2.5 2.4 2006 PSF yes

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 21

    2.5.1 2.5 2007 PSF yes2.5.2 2.5.2 2008 PSF yes

    Footnotes:

    (1) GPL-compatible doesn't mean that we're distributing Python underthe GPL. All Python licenses, unlike the GPL, let you distributea modified version without making your changes open source. TheGPL-compatible licenses make it possible to combine Python withother software that is released under the GPL; the others don't.

    (2) According to Richard Stallman, 1.6.1 is not GPL-compatible,because its license has a choice of law clause. According toCNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1is "not incompatible" with the GPL.

    Thanks to the many outside volunteers who have worked under Guido'sdirection to make these releases possible.

    B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON===============================================================

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

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

    2. Subject to the terms and conditions of this License Agreement, PSFhereby grants Licensee a nonexclusive, royalty-free, world-widelicense to reproduce, analyze, test, perform and/or display publicly,prepare derivative works, distribute, and otherwise use Pythonalone or in any derivative version, provided, however, that PSF'sLicense Agreement and PSF's notice of copyright, i.e., "Copyright (c)2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Python Software Foundation;All Rights Reserved" are retained in Python alone or in any derivativeversion prepared by Licensee.

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

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

    5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHONFOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS ASA 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 materialbreach of its terms and conditions.

    7. Nothing in this License Agreement shall be deemed to create anyrelationship of agency, partnership, or joint venture between PSF andLicensee. This License Agreement does not grant permission to use PSFtrademarks or trade name in a trademark sense to endorse or promote

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 22

    products or services of Licensee, or any third party.

    8. By copying, installing or otherwise using Python, Licenseeagrees to be bound by the terms and conditions of this LicenseAgreement.

    BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0-------------------------------------------

    BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1

    1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having anoffice at 160 Saratoga Avenue, Santa Clara, CA 95051, and theIndividual or Organization ("Licensee") accessing and otherwise usingthis software in source or binary form and its associateddocumentation ("the Software").

    2. Subject to the terms and conditions of this BeOpen Python LicenseAgreement, BeOpen hereby grants Licensee a non-exclusive,royalty-free, world-wide license to reproduce, analyze, test, performand/or display publicly, prepare derivative works, distribute, andotherwise use the Software alone or in any derivative version,provided, however, that the BeOpen Python License is retained in theSoftware, alone or in any derivative version prepared by Licensee.

    3. BeOpen is making the Software available to Licensee on an "AS IS"basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS ORIMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO ANDDISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESSFOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOTINFRINGE ANY THIRD PARTY RIGHTS.

    4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THESOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSSAS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANYDERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

    5. This License Agreement will automatically terminate upon a materialbreach of its terms and conditions.

    6. This License Agreement shall be governed by and interpreted in allrespects by the law of the State of California, excluding conflict oflaw provisions. Nothing in this License Agreement shall be deemed tocreate any relationship of agency, partnership, or joint venturebetween BeOpen and Licensee. This License Agreement does not grantpermission to use BeOpen trademarks or trade names in a trademarksense to endorse or promote products or services of Licensee, or anythird party. As an exception, the "BeOpen Python" logos available athttp://www.pythonlabs.com/logos.html may be used according to thepermissions granted on that web page.

    7. By copying, installing or otherwise using the software, Licenseeagrees to be bound by the terms and conditions of this LicenseAgreement.

    CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1---------------------------------------1. This LICENSE AGREEMENT is between the Corporation for NationalResearch Initiatives, having an office at 1895 Preston White Drive,Reston, VA 20191 ("CNRI"), and the Individual or Organization("Licensee") accessing and otherwise using Python 1.6.1 software insource or binary form and its associated documentation.

    2. Subject to the terms and conditions of this License Agreement, CNRI

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 23

    hereby grants Licensee a nonexclusive, royalty-free, world-widelicense to reproduce, analyze, test, perform and/or display publicly,prepare derivative works, distribute, and otherwise use Python 1.6.1alone or in any derivative version, provided, however, that CNRI'sLicense Agreement and CNRI's notice of copyright, i.e., "Copyright (c)1995-2001 Corporation for National Research Initiatives; All RightsReserved" are retained in Python 1.6.1 alone or in any derivativeversion prepared by Licensee. Alternately, in lieu of CNRI's LicenseAgreement, Licensee may substitute the following text (omitting thequotes): "Python 1.6.1 is made available subject to the terms andconditions in CNRI's License Agreement. This Agreement together withPython 1.6.1 may be located on the Internet using the followingunique, persistent identifier (known as a handle): 1895.22/1013. ThisAgreement may also be obtained from a proxy server on the Internetusing the following URL: http://hdl.handle.net/1895.22/1013".

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

    4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS ORIMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO ANDDISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESSFOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOTINFRINGE ANY THIRD PARTY RIGHTS.

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

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

    7. This License Agreement shall be governed by the federalintellectual property law of the United States, including withoutlimitation the federal copyright law, and, to the extent suchU.S. federal law does not apply, by the law of the Commonwealth ofVirginia, excluding Virginia's conflict of law provisions.Notwithstanding the foregoing, with regard to derivative works basedon Python 1.6.1 that incorporate non-separable material that waspreviously distributed under the GNU General Public License (GPL), thelaw of the Commonwealth of Virginia shall govern this LicenseAgreement only as to issues arising under or with respect toParagraphs 4, 5, and 7 of this License Agreement. Nothing in thisLicense Agreement shall be deemed to create any relationship ofagency, partnership, or joint venture between CNRI and Licensee. ThisLicense Agreement does not grant permission to use CNRI trademarks ortrade name in a trademark sense to endorse or promote products orservices of Licensee, or any third party.

    8. By clicking on the "ACCEPT" button where indicated, or by copying,installing or otherwise using Python 1.6.1, Licensee agrees to bebound by the terms and conditions of this License Agreement.

    ACCEPT

    CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2--------------------------------------------------Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,The Netherlands. All rights reserved.

    Permission to use, copy, modify, and distribute this software and its

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 24

    documentation for any purpose and without fee is hereby granted,provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear insupporting documentation, and that the name of Stichting MathematischCentrum or CWI not be used in advertising or publicity pertaining todistribution of the software without specific, written priorpermission.

    STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TOTHIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLEFOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN ANACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUTOF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

    libiconv:This software package is covered under GNU General Public License Version 3. More about GeneralPublic License Version 3 can be found at http://www.gnu.org and is also stated as belowGNU General Public License Version 3

    Zlib:/* zlib.h -- interface of the 'zlib' general purpose compression library

    version 1.2.10, January 2nd, 2017

    Copyright (C) 1995-2017 Jean-loup Gailly and Mark Adler

    This software is provided 'as-is', without any express or impliedwarranty. In no event will the authors be held liable for any damagesarising from the use of this software.

    Permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:

    1. The origin of this software must not be misrepresented; you must notclaim that you wrote the original software. If you use this softwarein a product, an acknowledgment in the product documentation would beappreciated but is not required.

    2. Altered source versions must be plainly marked as such, and must not bemisrepresented as being the original software.

    3. This notice may not be removed or altered from any source distribution.

    Jean-loup Gailly Mark [email protected] [email protected]

    */

    bzip2:This program, "bzip2", the associated library "libbzip2", and all documentation, are copyright (C) 1996-2010 Julian R Seward. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted providedthat the following conditions are met:

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

    2. The origin of this software must not be misrepresented; you must not claim that you wrote the originalsoftware. If you use this software in a product, an acknowledgment in the product documentation wouldbe appreciated but is not required.

    3. Altered source versions must be plainly marked as such, and must not be misrepresented as beingthe original software.

    4. The name of the author may not be used to endorse or promote products derived from this softwarewithout specific prior written permission.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 25

    THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NOEVENT SHALL THE AUTHOR 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 OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISEDOF THE POSSIBILITY OF SUCH DAMAGE.

    Julian Seward, [email protected] bzip2/libbzip2 version 1.0.6 of 6 September 2010

    sqlite:All of the code and documentation in SQLite has been dedicated to the public domain by the authors. Allcode authors, and representatives of the companies they work for, have signed affidavits dedicatingtheir contributions to the public domain and originals of those signed affidavits are stored in a firesafe atthe main offices of Hwaci. Anyone is free to copy, modify, publish, use, compile, sell, or distribute theoriginal SQLite code, either in source code form or as a compiled binary, for any purpose, commercial ornon-commercial, and by any means.

    The previous paragraph applies to the deliverable code and documentation in SQLite - those parts ofthe SQLite library that you actually bundle and ship with a larger application. Some scripts used as partof the build process (for example the "configure" scripts generated by autoconf) might fall under otheropen-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 yourrights 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 otherprojects or from the open internet. Every line of code can be traced back to its original author, and all ofthose authors have public domain dedications on file. So the SQLite code base is clean and isuncontaminated with licensed code from other projects.

    Termcap:This is free documentation; you can redistribute it and/ormodify it under the terms of the GNU General Public License aspublished by the Free Software Foundation; either version 2 ofthe License, or (at your option) any later version.

    The GNU General Public License's references to "object code"and "executables" are to be interpreted as the output of anydocument formatting or typesetting system, includingintermediate and printed output.

    This manual is distributed in the hope that it will be useful,but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See theGNU General Public License for more details.

    You should have received a copy of the GNU General PublicLicense along with this manual; if not, seehttp://www.gnu.org/licenses/

    unixODBC:This software package is covered under GNU Lesser General Public License Version 2.1. More aboutLesser General Public License Version 2.1 can be found at http://www.gnu.org and is also stated asbelowGNU Lesser General Public License Version 2.1

    hibernate:This software package is covered under GNU Lesser General Public License Version 2.1. More aboutLesser General Public License Version 2.1 can be found at http://www.gnu.org and is also stated asbelowGNU Lesser General Public License Version 2.1

    http://www.gnu.org/licenses/

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 26

    apache_commons:This software package is covered under Apache License Version 1.1. More about Apache LicenseVersion 1.1 can be found at http://www.apache.org/licenses and is also stated as belowApache License Version 1.1

    junit:Eclipse Public License - v 1.0

    THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLICLICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAMCONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

    1. DEFINITIONS

    "Contribution" means:

    a) in the case of the initial Contributor, the initial code and documentation distributed under thisAgreement, andb) in the case of each subsequent Contributor:i) changes to the Program, andii) additions to the Program;

    where such changes and/or additions to the Program originate from and are distributed by that particularContributor. A Contribution 'originates' from a Contributor if it was added to the Program by suchContributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions tothe Program which: (i) are separate modules of software distributed in conjunction with the Programunder their own license agreement, and (ii) are not derivative works of the Program."Contributor" means any person or entity that distributes the Program."Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed bythe use or sale of its Contribution alone or when combined with the Program."Program" means the Contributions distributed in accordance with this Agreement."Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

    2. GRANT OF RIGHTSa) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive,worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display,publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and suchderivative works, in source code and object code form.b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive,worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import andotherwise transfer the Contribution of such Contributor, if any, in source code and object code form. Thispatent license shall apply to the combination of the Contribution and the Program if, at the time theContribution is added by the Contributor, such addition of the Contribution causes such combination tobe covered by the Licensed Patents. The patent license shall not apply to any other combinations whichinclude the Contribution. No hardware per se is licensed hereunder.c) Recipient understands that although each Contributor grants the licenses to its Contributions set forthherein, no assurances are provided by any Contributor that the Program does not infringe the patent orother intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipientfor claims brought by any other entity based on infringement of intellectual property rights or otherwise.As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumessole responsibility to secure any other intellectual property rights needed, if any. For example, if a thirdparty patent license is required to allow Recipient to distribute the Program, it is Recipient'sresponsibility to acquire that license before distributing the Program.d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, ifany, to grant the copyright license set forth in this Agreement.

    3. REQUIREMENTSA Contributor may choose to distribute the Program in object code form under its own licenseagreement, provided that:a) it complies with the terms and conditions of this Agreement; andb) its license agreement:i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied,including warranties or conditions of title and non-infringement, and implied warranties or conditions ofmerchantability and fitness for a particular purpose;

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 27

    ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect,special, incidental and consequential damages, such as lost profits;iii) states that any provisions which differ from this Agreement are offered by that Contributor alone andnot by any other party; andiv) states that source code for the Program is available from such Contributor, and informs licenseeshow to obtain it in a reasonable manner on or through a medium customarily used for softwareexchange.

    When the Program is made available in source code form:a) it must be made available under this Agreement; andb) a copy of this Agreement must be included with each copy of the Program.

    Contributors may not remove or alter any copyright notices contained within the Program.Each Contributor must identify itself as the originator of its Contribution, if any, in a manner thatreasonably allows subsequent Recipients to identify the originator of the Contribution.

    4. COMMERCIAL DISTRIBUTIONCommercial distributors of software may accept certain responsibilities with respect to end users,business partners and the like. While this license is intended to facilitate the commercial use of theProgram, the Contributor who includes the Program in a commercial product offering should do so in amanner which does not create potential liability for other Contributors. Therefore, if a Contributorincludes the Program in a commercial product offering, such Contributor ("Commercial Contributor")hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against anylosses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actionsbrought by a third party against the Indemnified Contributor to the extent caused by the acts oromissions of such Commercial Contributor in connection with its distribution of the Program in acommercial product offering. The obligations in this section do not apply to any claims or Losses relatingto any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributormust: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow theCommercial Contributor to control, and cooperate with the Commercial Contributor in, the defense andany related settlement negotiations. The Indemnified Contributor may participate in any such claim at itsown expense.For example, a Contributor might include the Program in a commercial product offering, Product X. ThatContributor is then a Commercial Contributor. If that Commercial Contributor then makes performanceclaims, or offers warranties related to Product X, those performance claims and warranties are suchCommercial Contributor's responsibility alone. Under this section, the Commercial Contributor wouldhave to defend claims against the other Contributors related to those performance claims andwarranties, and if a court requires any other Contributor to pay any damages as a result, theCommercial Contributor must pay those damages.

    5. NO WARRANTYEXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ONAN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESSOR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. EachRecipient is solely responsible for determining the appropriateness of using and distributing the Programand assumes all risks associated with its exercise of rights under this Agreement , including but notlimited to the risks and costs of program errors, compliance with applicable laws, damage to or loss ofdata, programs or equipment, and unavailability or interruption of operations.

    6. DISCLAIMER OF LIABILITYEXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANYCONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATIONLOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OFANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGES.

    7. GENERALIf any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect thevalidity or enforceability of the remainder of the terms of this Agreement, and without further action bythe parties hereto, such provision shall be reformed to the minimum extent necessary to make suchprovision valid and enforceable.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 28

    If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in alawsuit) alleging that the Program itself (excluding combinations of the Program with other software orhardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b)shall terminate as of the date such litigation is filed.All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the materialterms or conditions of this Agreement and does not cure such failure in a reasonable period of time afterbecoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate,Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable.However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating tothe Program shall continue and survive.Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoidinconsistency the Agreement is copyrighted and may only be modified in the following manner. TheAgreement Steward reserves the right to publish new versions (including revisions) of this Agreementfrom time to time. No one other than the Agreement Steward has the right to modify this Agreement.The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign theresponsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of theAgreement will be given a distinguishing version number. The Program (including Contributions) mayalways be distributed subject to the version of the Agreement under which it was received. In addition,after a new version of the Agreement is published, Contributor may elect to distribute the Program(including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b)above, Recipient receives no rights or licenses to the intellectual property of any Contributor under thisAgreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program notexpressly granted under this Agreement are reserved.This Agreement is governed by the laws of the State of New York and the intellectual property laws ofthe United States of America. No party to this Agreement will bring a legal action under this Agreementmore than one year after the cause of action arose. Each party waives its rights to a jury trial in anyresulting litigation.

    struts:This software package is covered under Apache License Version 2.0. More about Apache LicenseVersion 2.0 can be found at http://www.apache.org/licenses and is also stated as belowApache License Version 2.0

    Sendmail:

    SENDMAIL LICENSE

    The following license terms and conditions apply, unless a redistributionagreement or other license is obtained from Sendmail, Inc., 6475 ChristieAve, Third Floor, Emeryville, CA 94608, USA, or by electronic mail [email protected].

    License Terms:

    Use, Modification and Redistribution (including distribution of anymodified or derived work) in source and binary forms is permitted only ifeach of the following conditions is met:

    1. Redistributions qualify as "freeware" or "Open Source Software" underone of the following terms:

    (a) Redistributions are made at no charge beyond the reasonable cost ofmaterials and delivery.

    (b) Redistributions are accompanied by a copy of the Source Code or by anirrevocable offer to provide a copy of the Source Code for up to threeyears at the cost of materials and delivery. Such redistributionsmust allow further use, modification, and redistribution of the SourceCode under substantially the same terms as this license. For thepurposes of redistribution "Source Code" means the complete compilableand linkable source code of sendmail and associated libraries andutilities in the sendmail distribution including all modifications.

    2. Redistributions of Source Code must retain the copyright notices as theyappear in each Source Code file, these license terms, and thedisclaimer/limitation of liability set forth as paragraph 6 below.

  • LEGAL AND COMPLIANCE | Third Party Notifications

    Third Party Terms and Notifications v2.1, June2017 Page 29

    3. Redistributions in binary form must reproduce the Copyright Notice,these license terms, and the disclaimer/limitation of liability setforth as paragraph 6 below, in the documentation and/or other materialsprovided with the distribution. For the purposes of binary distributionthe "Copyright Notice" refers to the following language:"Copyright (c) 1998-2012 Sendmail, Inc. All rights reserved."

    4. Neither the name of Sendmail, Inc. nor the University of California nornames of their contributors may be used to endorse or promoteproducts derived from this software without specific prior writtenpermission. The name "sendmail" is a trademark of Sendmail, Inc.

    5.