DOCSLIB.ORG

Red Hat Enterprise Linux 7 Windows Integration Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Red Hat Enterprise Linux 7 Windows Integration Guide Red Hat Enterprise Linux 7 Windows Integration Guide Integrating Linux Systems with Active Directory Environments Ella Deon Ballard Red Hat Enterprise Linux 7 Windows Integration Guide Integrating Linux Systems with Active Directory Environments Ella Deon Ballard [email protected] Legal Notice Copyright © 2014 Red Hat. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract Identity and policy management — for both users and machines — is a core function for almost any enterprise environment. Identity Management provides a way to create an identity domain that allows machines to enroll to a domain and immediately access identity information required for single sign-on and authentication services, as well as policy settings that govern authorization and access. This manual covers all aspects of installing, configuring, and managing Identity Management domains, including both servers and clients. This guide is intended for IT and systems administrators. Table of Contents Table of Contents .P .r .e .f a. c. e. 3. ⁠1. Information for Managing Identity and Authentication Policies in Linux 3 ⁠2. Audience and Purpose 3 ⁠3. Giving Feedback 3 ⁠4. Document Change History 4 ⁠.C .h . a. p. t. e. r. 1. .W . a. y. s. .t .o . I.n .t .e .g .r .a .t e. A. c. t. i.v .e . D. .i r.e .c .t .o .r .y . a. n. d. .L . i.n .u .x . E. .n .v .i r.o . n. m. .e .n .t .s . 5. ⁠1.1. Defining Windows Integration 5 ⁠1.2. Small Environments: Using Windows as an Identity Source 6 ⁠1.3. Small Environments: Enrolling Individual Clients 6 ⁠1.4. Big Environments: Synchronizing Users 7 ⁠1.5. Big Environments: Trusted Realms 7 ⁠.P .a .r .t .I .. A. .d .d .i n. .g . a. .S . i.n .g .l e. .L . i.n .u .x . S. .y .s .t e. m. t. o. .a .n . .A .c .t .i v. e. .D . i.r e. c. t. o. r. y. .D .o . m. .a .i n. 9. ⁠.C .h . a. p. t. e. r. 2. .U .s .i n. g. A. c. t. i.v .e . D. .i r.e .c .t .o .r .y . a. s. .a .n . I.d . e. n. t. i.t y. .P . r.o .v .i d. .e .r .f .o .r .S . S. S. .D . 1. 0. ⁠2.1. About SSSD 10 ⁠2.2. Environments for SSSD 12 ⁠2.3. How SSSD Integrates with an Active Directory Environment 12 ⁠2.4. Configuring an Active Directory Domain with ID Mapping 16 ⁠2.5. Configuring an Active Directory Domain with POSIX Attributes 19 ⁠2.6. Configuring Active Directory as an LDAP Domain 23 ⁠2.7. Additional Configuration Examples 26 ⁠.C .h . a. p. t. e. r. 3. .. U. .s .i n. g. .r .e .a .l m. .d . .t o. .C . o. n. .n .e .c .t . t.o . a. .n . A. c. t. i.v .e . D. .i r.e . c. t.o .r .y . D. .o .m . a. i.n . 3. 1. ⁠3.1. About realmd 31 ⁠3.2. realmd Commands 31 ⁠3.3. Discovering and Joining Active Directory Domains 32 ⁠3.4. Managing User Logins from Active Directory 34 ⁠3.5. Adding Default User Configuration 34 ⁠3.6. Additional Configuration for the Active Directory Domain Entry 35 ⁠.C .h . a. p. t. e. r. 4. .. .U .s .i n. .g . S. a. .m . b. a. ,. K. .e .r b. .e .r o. .s ., .a .n .d . W. i.n .b .i n. d. 3. 7. ⁠4.1. About Samba and Active Directory Authentication 37 ⁠4.2. Summary of Configuration Files, Options, and Packages 40 ⁠4.3. Configuring a Domain Member Using authconfig 42 ⁠.P .a .r .t .I I.. .I n. .t e. g. .r a. t. i.n .g . a. L. i.n .u .x . D. .o .m . a. .i n. .w . i.t h. .a . n. .A .c .t .i v. e. .D . i.r e. .c .t o. r. y. .D . o. m. .a .i n. 4. 8. ⁠.C .h . a. p. t. e. r. 5. .C .r .e .a .t .i n. g. .C . r. o. s. s. -.R . e. a. l.m . .T . r.u . s. t.s . w. .i t.h . .A .c .t .i v. e. .D . i.r e. c. t. o. r. y. .a .n .d . I.d . e. n. t. i.t y. .M . a. n. .a .g .e .m . e. .n .t . ⁠5.1. The Meaning of "Trust" 49 4 9 ⁠5.2. Environment and Machine Requirements to Set up Trusts 59 ⁠5.3. Creating Trusts 62 ⁠5.4. Creating IdM Groups for Active Directory Users 84 ⁠5.5. Maintaining Trusts 86 ⁠5.6. Verifying That IdM Machines Have Resolvable Names 90 ⁠5.7. Setting PAC Types for Services 91 ⁠5.8. Using SSH from Active Directory Machines for IdM Resources 94 ⁠5.9. Using Trust with Kerberized Web Applications 95 ⁠.C .h . a. p. t. e. r. 6. .S .e .t .t i.n . g. .u .p . K. .e .r .b .e .r .o .s . C. .r o. s. s. -. R. e. .a .l m. A. u. .t h. e. .n .t i.c .a . t.i o. n. 9. 7. ⁠6.1. A Trust Relationship 97 ⁠6.2. Setting up a Realm Trust 100 ⁠.C .h . a. p. t. e. r. 7. .S .y .n .c .h . r.o .n . i.z .i n. g. .A . c. t.i v. e. .D . i.r .e .c .t o. .r y. .a .n . d. .I d. e. n. .t i.t .y . M. .a .n .a .g . e. m. .e .n .t . U. s. e. .r s. 1. 0. 1. ⁠7.1. Supported Windows Platforms 101 ⁠7.2. About Active Directory and Identity Management 101 ⁠7.3. About Synchronized Attributes 103 1 Red Hat Enterprise Linux 7 Windows Integration Guide ⁠7.3. About Synchronized Attributes 103 ⁠7.4. Setting up Active Directory for Synchronization 107 ⁠7.5. Managing Synchronization Agreements 107 ⁠7.6. Managing Password Synchronization 115 ⁠.I n. d. e. x. 1. 2. 0. ..
Load more

Recommended publications
  • Open Directory & Openldap
    Open Directory & OpenLDAP David M. O’Rourke Engineering Manager Overview • Background on Apple’s Open Directory Technology (8 minutes) – What is it – What is Directory Services • How has Apple integrated OpenLDAP (20 minutes or less) – what has Apple added to OpenLDAP? • Questions and Answers (remaining time) Open Directory • Open Directory is a technology name – Covers both client access technologies and server technologies – Integrates and promotes industry standard technologies • Open Directory is built into Mac OS X & Mac OS X Server – Been there since 10.0 • Open Sourced as part of Darwin – http://developer.apple.com/darwin/projects/ opendirectory/ What Is Directory Services • Abstraction API for read/write access to system configuration and management data – Users, groups, mount records and others – Authentication abstraction Mac OS X Software Directory Services NetInfo LDAP BSD Files Other… Directory Services in 10.3 • Includes – LDAPv3 (read/write), Native Active Directory, NetInfo, NIS, BSD/etc files – Service Discovery: Rendezvous, SMB, AppleTalk, and SLP – LDAPv3 client support replication fail over • Documented Access API and plug-in API – SDK posted – Sample code, sample plug-in, notes – Directory Services Headers are installed in – /System/Library/Frameworks/DirectoryService.framework – Command line tool for directory editing ‘dscl’ 10.3 Usage of Directory Services • Login Window uses Directory Services for all user authentication – Managed Desktop • All Security Framework authentication uses Directory Services • Legacy Unix
    [Show full text]
  • Red Hat Jboss Developer Studio
    RED HAT JBOSS DEVELOPER STUDIO DATASHEET BENEFITS EVERYTHING YOU NEED TO DEVELOP, TEST, AND DEPLOY RICH WEB, MOBILE WEB, AND ENTERPRISE APPLICATIONS AND SOA SERVICES. • Provides a pre-assembled ® ® development environment, Red Hat JBoss Developer Studio provides superior support for your entire development life including both tooling and cycle in a single tool. It is a certified Eclipse-based integrated development environment (IDE) for runtime components developing, testing, and deploying rich web applications, mobile web applications, transactional enterprise applications, and SOA-based integration applications and services. • Enables development of applications for deployment JBoss Developer Studio includes a broad set of tooling capabilities and support for multiple pro- on-premise or in the cloud gramming models and frameworks, including Java™ Enterprise Edition 6, RichFaces, JavaServer ® through its seamless inte- Faces (JSF), Enterprise JavaBeans (EJB), Java Persistence API (JPA), and Hibernate , JAX-RS gration with both OpenShift with RESTEasy, Contexts Dependency Injection (CDI), HTML5, and many other popular technolo- Enterprise by Red Hat and gies. It is fully tested and certified to ensure that all its plug-ins, runtime components, and their OpenShift Online by Red Hat dependencies are compatible with each other. • Certified updates so you JBoss Developer Studio provides developer choice in supporting multiple Java virtual machines don’t have to worry about (JVMs), productivity with Maven, and testing with Arquillian. It also includes all needed depen- updating parts that may dencies and third-party plugins. These pre-configured tools save time and offer significant value, not work with the rest of improving productivity and reducing deployment times. the environment Developers can have confidence that their development environment is stable, upgradeable, • Tested and certified to deployable, and supportable.
    [Show full text]
  • 5.7 Release Notes
    Red Hat Enterprise Linux 5 5.7 Release Notes Release Notes for Red Hat Enterprise Linux 5.7 Red Hat Inc. Red Hat Enterprise Linux 5 5.7 Release Notes Release Notes for Red Hat Enterprise Linux 5.7 Legal Notice Copyright © 2011 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
    [Show full text]
  • AWS Directory Service Setup with Netapp Cloud Volumes Service for AWS Prabu Arjunan, Netapp August 2019
    AWS Directory service setup with NetApp Cloud Volumes Service for AWS Prabu Arjunan, NetApp August 2019 Abstract This document provides instructions to help users set up the AWS directory services environment for using NetApp® Cloud Volumes Service for Amazon Web Services (AWS). TABLE OF CONTENTS 1 Overview ................................................................................................................................................ 3 2 Requirements ........................................................................................................................................ 3 3 Creating the AWS Active Directory service ....................................................................................... 4 4 Adding the Active Directory server to Cloud Volumes Service ..................................................... 10 5 Creating a cloud volume that uses the Active Directory server .................................................... 12 Common errors messages....................................................................................................................... 14 References ................................................................................................................................................. 14 Version History ......................................................................................................................................... 14 2 AWS Directory service setup with NetApp Cloud Volume Service for AWS © 2019 NetApp, Inc. All rights reserved. 1 Overview
    [Show full text]
  • Add-Ons for Red Hat Enterprise Linux
    DATASHEET ADD-ONS FOR RED HAT ENTERPRISE LINUX WORKLOAD AND MISSION-CRITICAL PLATFORM ENHANCEMENTS In conjunction with Red Hat® Enterprise Linux®, Red Hat offers a portfolio of Add-Ons to extend the features of your Red Hat Enterprise Linux subscription. Add-Ons to Red Hat Enterprise Linux tailor your application environment to suit your particular computing requirements. With increased flexibility and choice, customers can deploy what they need, when they need it. ADD-ON OPTIONS FOR AVAILABILITY MANAGEMENT High Availability Add-On Red Hat’s High Availability Add-On provides on-demand failover services between nodes within a cluster, making applications highly available. The High Availability Add-On supports up to 16 nodes and may be configured for most applications that use customizable agents, as well as for virtual guests. The High Availability Add-On also includes failover support for off-the-shelf applications like Apache, MySQL, and PostgreSQL. When using the High Availability Add-On, a highly available service can fail over from one node to another with no apparent interruption to cluster clients. The High Availability Add-On also ensures data integrity when one cluster node takes over control of a service from another clus- ter node. It achieves this by promptly evicting nodes from the cluster that are deemed to be faulty using a method called “fencing” that prevents data corruption. www.redhat.com DATASHEET ADD-ONS For RED Hat ENterprise LINUX 6 Resilient Storage Add-On Red Hat’s Resilient Storage Add-On enables a shared storage or clustered file system to access the same storage device over a network.
    [Show full text]
  • White Paper | September 2 0 1 7
    Oracle Directory Services Buyer’s Guide ORACLE WHITE PAPER | SEPTEMBER 2 0 1 7 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. ORACLE DIRECTORY SERVICES – BUYER’S GUIDE Table of Contents Introduction 1 Business Drivers 2 Oracle Directory Services 3 Key Considerations for Some Popular Scenarios 4 Cloud 4 Mobile 4 Customer-Facing Internet 4 Employee-Facing Intranet 5 Directory Services Checklist 5 Conclusion 7 ORACLE DIRECTORY SERVICES – BUYER’S GUIDE Introduction In the late 1990s, directory servers were essentially designed as white-page applications for providing users with secure access to enterprise resources through authentication and authorization processes. Since then, their use has been extended to partners and customers, thus creating the need to support an increasing number of diverse users and communities. Today, directory services need to accommodate hundreds of millions of users and provide additional services to break identity silos. With the ubiquitous use of mobile devices as well as cloud deployments and the integration of social networks identities into the enterprise fabric, billions of objects are transacted everyday through directory services. Modern directory services now go beyond the initial capability to store objects in an identity repository. Directory solutions have evolved around three foundation services: » Storage: Persisting and maintaining entries representing identities.
    [Show full text]
  • Questions for Openshift
    www.YoYoBrain.com - Accelerators for Memory and Learning Questions for OpenShift Category: Default - (402 questions) OpenShift:  2 primary tools to serve 1. container runtime - creates containers in application in OpenShift platform Linux 2. orchestration engine - manage cluster of servers running containers OpenShift:  routing layer a software load balancer, when an application is deployed in OpenShift, a DNS entry is created and added to the load balancer, which interfaces with the Kubernetes service OpenShift:  log into cluster and create oc login -u dev -p dev http://....:8443 user named dev with password dev OpenShift:  what is the default port for 8443 OpenShift cluster OpenShift:  what is a cluster's initial All All identity provider user name/password configuration allows any user and password combination to log in. OpenShift:  ____ are the fundamental projects way applications are organized OpenShift:  to create a project called oc new-project image-update image-update --display-name='My image update project' OpenShift:  how to change to project oc project myProj myProj OpenShift:  each application application source code deployment's image is created using _____ custom base image called a builder image and ____ OpenShift:  the component that build config controls the creation of your application containers is _____ OpenShift:  ____ contains all the info build config needed to build an application using its source code OpenShift:  4 things in build config 1. URL for the application source code 2. Name of builder image to use 3. Name of the application container image that is created 4.
    [Show full text]
  • The 12 Essential Tasks of Active Directory Domain Services
    WHITE PAPER ACTIVE DIRECTORY DOMAIN SERVICES The 12 Essential Tasks of Active Directory Domain Services Using the right tools and processes helps reduce administrative overhead and ensures directory service is always available By Nelson Ruest and Danielle Ruest Sponsored by WHITE PAPER ACTIVE DIRECTORY DOMAIN SERVICES ABSTRACT Active Directory Domain Services (AD DS) administration and management includes Sponsored by 12 major tasks. These tasks cover a wide breadth of business needs and are not all performed solely by AD DS administrators. In fact, administrators can and should delegate several tasks to other members of their technical community, technicians, help desk personnel, even users such as team managers and administrative assistants. While delegation is a way to reduce the amount of work administrators have to do when managing AD DS infrastructures, it really only addresses one or two of the 12 tasks, for example, user and group administration as well as end point device administration. The other ten tasks can be staggering in nature—security, networked service administration, OU-Specific Management, Group Policy Object management and many more—and because of this can take up inordinate amounts of time. You can rely on Microsoft’s built-in tools to reduce some of this workload, but are the native tools enough? Perhaps it’s time to reduce AD DS administration overhead by automating most tasks and tightening internal security. Address this by first, determining what the twelve essential labors of Active Directory are and then, see how you can reduce AD DS workloads through the implementation of proper management and administration tools.
    [Show full text]
  • Integrating Openshift Enterprise with Identity Management (Idm) in Red Hat Enterprise Linux
    Integrating OpenShift Enterprise with Identity Management (IdM) in Red Hat Enterprise Linux OpenShift Enterprise 2.2 IdM in Red Hat Enterprise Linux 7 Windows Server 2012 - Active Directory Integration Mark Heslin Principal Systems Engineer Version 1.1 January 2015 1801 Varsity Drive™ Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. © 2014 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liable for technical or editorial errors or omissions contained herein. Distribution of modified versions of this document is prohibited without the explicit permission of Red Hat Inc. Distribution of this work or derivative of this work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from Red Hat Inc.
    [Show full text]
  • Vulnerability Summary for the Week of June 5, 2017
    Vulnerability Summary for the Week of June 5, 2017 Please Note: • The vulnerabilities are categorized by their level of severity which is either High, Medium or Low. • The CVE identity number is the publicly known ID given to that particular vulnerability. Therefore, you can search the status of that particular vulnerability using that ID. • The CVSS (Common Vulnerability Scoring System) score is a standard scoring system used to determine the severity of the vulnerability. High Vulnerabilities Primary CVSS Source & Patch Vendor -- Product Description Published Score Info In Apache Hadoop 2.8.0, 3.0.0-alpha1, and 3.0.0-alpha2, the LinuxContainerExecutor runs docker commands as root with CVE-2017-7669 insufficient input validation. When the docker BID(link is feature is enabled, authenticated users can run 2017-06- external) apache -- hadoop commands as root. 04 8.5 MLIST CVE-2017-9364 Unrestricted File Upload exists in BigTree CONFIRM(link CMS through 4.2.18: if an attacker uploads an is external) bigtreecms -- 'xxx.pht' or 'xxx.phtml' file, they could bypass 2017-06- CONFIRM(link bigtree_cms a safety check and execute any code. 02 7.5 is external) CVE-2017-9435 Dolibarr ERP/CRM before 5.0.3 is vulnerable CONFIRM(link to a SQL injection in user/index.php is external) (search_supervisor and search_statut 2017-06- CONFIRM(link dolibarr -- dolibarr parameters). 05 7.5 is external) CVE-2014-9923 In NAS in all Android releases from CAF BID(link is using the Linux kernel, a Buffer Copy external) without Checking Size of Input vulnerability 2017-06- CONFIRM(link google -- android could potentially exist.
    [Show full text]
  • [MS-DSSP]: Directory Services Setup Remote Protocol
    [MS-DSSP]: Directory Services Setup Remote Protocol Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • Open Directory Administration for Version 10.5 Leopard Second Edition
    Mac OS X Server Open Directory Administration For Version 10.5 Leopard Second Edition Apple Inc. © 2008 Apple Inc. All rights reserved. The owner or authorized user of a valid copy of Mac OS X Server software may reproduce this publication for the purpose of learning to use such software. No part of this publication may be reproduced or transmitted for commercial purposes, such as selling copies of this publication or for providing paid-for support services. Every effort has been made to make sure that the information in this manual is correct. Apple Inc., is not responsible for printing or clerical errors. Apple 1 Infinite Loop Cupertino CA 95014-2084 www.apple.com The Apple logo is a trademark of Apple Inc., registered in the U.S. and other countries. Use of the “keyboard” Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. Apple, the Apple logo, iCal, iChat, Leopard, Mac, Macintosh, QuickTime, Xgrid, and Xserve are trademarks of Apple Inc., registered in the U.S. and other countries. Finder is a trademark of Apple Inc. Adobe and PostScript are trademarks of Adobe Systems Incorporated. UNIX is a registered trademark of The Open Group. Other company and product names mentioned herein are trademarks of their respective companies. Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation. Apple assumes no responsibility with regard to the performance or use of these products.
    [Show full text]