Release Notes for McAfee(R) Quarantine Manager(TM) Version 6.0 Copyright (C) 2008 McAfee, Inc. All Rights Reserved ========================================================== Thank you for using McAfee Quarantine Manager(TM) software. This file contains important information regarding this release. We recommend that you read the entire document. IMPORTANT: McAfee recommends that you use any pre-release software in a test environment only. McAfee does not support automatic upgrading of a pre-release version of the software. To upgrade to a later Beta release, a Release Candidate, or a production release of the software, you must uninstall the existing version of the software. McAfee Quarantine Manager version 6.0 software expires on January 15, 2009. _________________________________________________________ WHAT'S IN THIS FILE - About McAfee Quarantine Manager - New Features - Installation and System Requirements - Installation - Integration with ePolicy Orchestrator 4.0 - Testing your installation - Uninstallation - Known Issues - Additional Information - Documentation - Contact Information - Copyright and Trademark Attributions - License Information _________________________________________________________ ABOUT MCAFEE QUARANTINE MANAGER McAfee Quarantine Manager consolidates quarantine and anti-spam management functionality. It gives you a central point from which you can analyze and act upon emails and files that have been quarantined, because they are spam, phish, viruses, potentially unwanted software or other undesirable content. It is effective in managing unsolicited bulk email or spam. No anti-spam filter is capable of detecting all of the spam that flows through a network. Occasionally some emails may incorrectly be identified as spam. Administrators and users increasingly want to tune anti-spam products to suit their own environments and increase the effectiveness of their spam filtering. McAfee Quarantine Manager allows administrators to: - Configure the storage and aging of quarantined items. - Manage email digests, databases and product logs. - Manage blacklists and whitelists, including specifying email addresses to be added to the blacklist or whitelist. - Decide which quarantined items, users can see. - Carry out tasks related to quarantined items such as releasing messages or submitting samples to McAfee labs. - Access domain specific quarantined items and user submissions. - Manage quarantined data related to specific domains. - Enable users to log on to McAfee Quarantine Manager using LDAP credentials in Active Directory or Lotus Domino. - Provide top 10 reports of the quarantined items. - Synchronize users with LDAP servers such as Active Directory or Lotus Domino. - Reassign quarantined items of one user to another. McAfee Quarantine Manager allows users to: - Maintain user’s McAfee Quarantine Manager account. - View and maintain a personal blacklist and whitelist. - Configure McAfee Quarantine Manager account for email aliases. - View quarantined items for any email aliases or/and re-assigned user. - Release quarantined messages that are incorrectly identified as spam. - Request administrator to release messages that are incorrectly identified as phish, potentially unwanted programs or unwanted content. - Specify how long the quarantined items should remain in the database before being purged. _________________________________________________________ NEW FEATURES - Support for Microsoft SQL Server 2005. - Support for Windows 2008 server. - Support for 64-bit Windows Server. - Integrated Windows Authentication. - Automatic synchronization with LDAP servers such as Active Directory or Lotus Domino. - Quick access to Top 10 Reports. - Manageability through McAfee ePolicy Orchestrator 4.0. - Improved Domain based quarantine. - Improved performance and usability. - DBSuite utility to convert from one database to another, maintain the database, configure the database and created bulk end-user accounts. _________________________________________________________ INSTALLATION AND SYSTEM REQUIREMENTS IMPORTANT: Do not install McAfee Quarantine Manager on the same server as ePolicy Orchestrator. You need to uninstall any previous versions of McAfee Quarantine Manager, then install McAfee Quarantine Manager version 6.0. MINIMUM SYSTEM REQUIREMENTS Server Operating System Supported: - Windows 2003 Standard/Enterprise Server SP2 (32-bit or 64-bit) - Windows 2003 Standard/Enterprise Server R2 (32-bit or 64-bit) - Windows 2008 Standard/Enterprise/Datacenter Server (32-bit or 64-bit) Databases Supported: - MySQL Server version 5.0 (packaged with this release) - Microsoft SQL Server 2005 Standard/Enterprise SP2 (32-bit or 64-bit) Windows Components Required: - Internet Information Service 6.0 (IIS) or later Processor Supported: - Intel Pentium 4, 2.8GHz, 400MHz front-side bus Memory: - 2 GB RAM Disk Space: - 160 GB with NTFS file system Browsers Supported: - Microsoft Internet Explorer 6.0 or 7.0 - Firefox 2.0 Network Requirement: - 10/100/1000 Mbps Ethernet card McAfee Product(s) Supported: - Secure Content Management version 4.5 or later _________________________________________________________ INSTALLATION INSTALLING MYSQL FOR MCAFEE QUARANTINE MANAGER 6.0 NOTE: "MySQL for McAfee Quarantine Manager" / Microsoft SQL Server 2005 and "McAfee Quarantine Manager" can be installed on two different servers or on the same server. You must install "MySQL for McAfee Quarantine Manager" / Microsoft SQL Server 2005 first. McAfee recommends you to install "MySQL for McAfee Quarantine Manager" / Microsoft SQL Server 2005 on a computer where no other database product is installed. 1. Extract "MQM_v6.0.ZIP" package on to a temporary directory. You will find the following folders: - McAfee Quarantine Manager - MySQL for McAfee Quarantine Manager - McAfee Quarantine Manager DB Suite - ePO 2. From "MySQL for McAfee Quarantine Manager" directory, extract "MQM60MySQL.ZIP" to a temporary directory and double-click "SETUP.EXE". 3. Click "Next" and follow the on-screen instructions. 4. In "Database Server Settings" dialog box, specify the following configuration settings for MySQL for McAfee Quarantine Manager: - Username. The default Username is "root". - Password. The default password is "root". - Database name. The default database name is "mqm". - Port number. The default port number is "3306". - McAfee Quarantine Manager Super Administrator Username and Password. The default user name is "super@mqm.com" and the default password is "super123". 5. In the "Ready to Install" dialog box, click "Next". 6. Click "Finish" to complete the installation. INSTALLING MCAFEE QUARANTINE MANAGER ASSUMPTIONS: Assumption 1: Ensure that "MySQL for McAfee Quarantine Manager 6.0" / Microsoft SQL Server 2005 is installed either on same computer or on a different computer. Assumption 2: Ensure that Microsoft SQL Server Native Client is installed on the McAfee Quarantine Manager server, if the Microsoft SQL Server 2005 is installed on a different computer. 1. Extract "MQM_v6.0.ZIP" package on to a temporary directory. You will find the following folders: - McAfee Quarantine Manager - MySQL for McAfee Quarantine Manager - McAfee Quarantine Manager DB Suite - ePO 2. From "McAfee Quarantine Manager" directory, extract "MQM60Server.ZIP" to a temporary directory and double-click "SETUP.EXE". 3. Follow the on-screen instructions to install the software. 4. Provide the Port number on which the Internet Information Services will host McAfee Quarantine Manager website. The default value is "80". 5. Click "Finish" to complete the installation. 6. A message box notifies you to restart the computer. Click "Yes". INSTALLING MCAFEE QUARANTINE MANAGER DB SUITE UTILITY ASSUMPTIONS: Assumption 1: Ensure that "MySQL for McAfee Quarantine Manager 6.0" / Microsoft SQL Server 2005 is installed either on same computer or on a different computer. Assumption 2: Ensure that Microsoft SQL Server Native Client is installed on the server where the DB Suite utility will be installed, if the Microsoft SQL Server 2005 is installed on a different computer. 1. Extract "MQM_v6.0.ZIP" package on to a temporary directory. You will find the following folders: - McAfee Quarantine Manager - MySQL for McAfee Quarantine Manager - McAfee Quarantine Manager DB Suite - ePO 2. From "McAfee Quarantine Manager DB Suite" directory, extract "MQM60DBSuite.ZIP" to a temporary directory and double-click "SETUP.EXE". 3. Follow the on-screen instructions to install the software. 4. Click "Finish" to complete the installation. _________________________________________________________ INTEGRATING MCAFEE QUARANTINE MANAGER WITH EPOLICY ORCHESTRATOR VERSION 4.0 1. Using an administrator account, log on to the ePolicy Orchestrator server. 2. Create a temporary directory on your local drive. 3. Extract "MQM_v6.0.ZIP" package on to a temporary directory. You will find the following folders: - McAfee Quarantine Manager - MySQL for McAfee Quarantine Manager - McAfee Quarantine Manager DB Suite - ePO NOTE: Use "MQM6POLICIES.ZIP" and "MQM6REPORTS.ZIP" found in the ePO folder to install the ePolicy Orchestrator extensions. 4. Load ePolicy Orchestrator. Log on to the ePolicy Orchestrator server console using the administrator account. CHECKING-IN MCAFEE QUARANTINE MANAGER PACKAGE 5. Click Software | Check In Package. The Package page appears. 6. Choose the Package type as Product or Update (.ZIP) and browse in File path to locate "MQM60Server.ZIP" saved in McAfee Quarantine Manager folder. 7. Click Next. The Package Options page appears with the Package info. 8. Choose a Branch. 9. In Options, select the required option(s), then click Save. CHECKING-IN MYSQL FOR MCAFEE QUARANTINE MANAGER PACKAGE 10. Click Software | Check In Package. The Package page appears. 11. Choose the Package type as Product or Update (.ZIP) and browse in File path to locate "MQM60MySQL.ZIP" saved in a MySQL for McAfee Quarantine Manager folder. 12. Click Next. The Package Options page appears with the Package info. 13. Choose a Branch. 14. In Options, select the required option(s), then click Save. INSTALLING MCAFEE QUARANTINE MANAGER WITH DEFAULT SETTINGS ON THE CLIENT COMPUTERS 15. Click Systems | System Tree | Client Tasks | New Task. 16. Type a Name, Notes for the task and choose the Type as Product Deployment (McAfee Agent). 17. Click Next. The Client Task Builder page appears. 18. Under Description, select the Target Platforms. 19. In Products to deploy, select "McAfee Quarantine Manager 6.0" from the drop-down and choose the Action as "Install". 20. In Options, select or deselect these options as required: - Run this task at every policy enforcement interval (Windows only). - Run update after successful product deployment (4.0 or above). 21. Click Next to schedule this task as desired. 22. Click Next to view a summary of the task. 23. Click Save and send an agent wake-up call. INSTALLING MYSQL FOR MCAFEE QUARANTINE MANAGER WITH DEFAULT SETTINGS ON THE CLIENT COMPUTERS 24. Click Systems | System Tree | Client Tasks | New Task. 25. Type a Name, Notes for the task and choose the Type as Product Deployment (McAfee Agent). 26. Click Next. The Client Task Builder page appears. 27. Under Description, select the Target Platforms. 28. In Products to deploy, select "MySQL for McAfee Quarantine Manager 6.0" from the drop-down and choose the Action as "Install". 29. In Options, select or deselect these options as required: - Run this task at every policy enforcement interval (Windows only). - Run update after successful product deployment (4.0 or above). 30. Click Next to schedule this task as desired. 31. Click Next to view a summary of the task. 32. Click Save and send an agent wake-up call. INSTALLING MCAFEE QUARANTINE MANAGER POLICY EXTENSIONS 33. Click Configuration | Install Extension. The Install Extension dialog box appears. 34. Click Browse, select the extension file "MQM6POLICIES.ZIP" and click OK. NOTE: If you are managing more than one McAfee Quarantine Manager server using ePolicy Orchestrator, you should have a separate database configuration policy assigned for each of the servers. This avoids conflicts between the servers trying to connect to the same database. To enforce different policies on different servers: a. Create a New Policy for Database Configuration and type a policy name. b. Change the database connectivity details and click Save. c. From Systems Tree, select the target McAfee Quarantine Manager server and click Assign Policy. d. Select the product as McAfee Quarantine Manager 6.0 and the category as Database Configuration. e. Select the newly created policy and click Save. f. Send an agent wake-up call. g. Repeat the same steps to enforce different policies on different servers. INSTALLING MCAFEE QUARANTINE MANAGER REPORT EXTENSIONS 35. Click Configuration | Install Extension. The Install Extension dialog box appears. 36. Click Browse, select the extension file "MQM6REPORTS.ZIP" and click OK. _________________________________________________________ UNINSTALLING MCAFEE QUARANTINE MANAGER USING EPOLICY ORCHESTRATOR 4.0 REMOVING MCAFEE QUARANTINE MANAGER FROM THE CLIENT COMPUTER 1. Using an administrative account, log on to the ePolicy Orchestrator server. 2. Click Systems | System Tree and choose a desired group. 3. From the Client Tasks tab, click New Task. 4. Type a Name, Notes for the task and choose the Type as "Product Deployment (McAfee Agent)", then click Next. 5. In Configuration, select the Target Platforms as Windows, "McAfee Quarantine Manager 6.0" as Products & Components, Action as "Remove" and an appropriate Language. 6. To remove MySQL for McAfee Quarantine Manager, repeat Steps 1 to 4, then in Configuration, select the Target Platforms as Windows, "MySQL for McAfee Quarantine Manager 6.0" as Products & Components, Action as "Remove" and an appropriate Language. 7. Select or deselect "Run this task at every policy enforcement interval (Windows only)". 8. Click Next and schedule the task as desired. 9. Click Next to view a summary of the task, then click Save. 10. Send an agent wake-up call. REMOVING THE PACKAGE FROM THE EPOLICY ORCHESTRATOR 1. Using an administrative account, log on to the ePolicy Orchestrator server. 2. Click Software | Master Repository. 3. Click the Delete link of the McAfee Quarantine Manager. 4. To remove "MySQL for McAfee Quarantine Manager" package, repeat Steps 2 and 3, then delete the link of "MySQL for McAfee Quarantine Manager". REMOVING THE PRODUCT EXTENSION 1. Using an administrative account, log on to the ePolicy Orchestrator server. 2. Click "Configuration". 3. Choose the extension file "McAfee Quarantine Manager" and click "Remove". 4. Select the option "Force removal, bypassing any checks or errors" and click OK. REMOVING THE REPORTS EXTENSION 1. Using an administrative account, log on to the ePolicy Orchestrator server. 2. Click "Configuration". 3. Choose the extension file "McAfee Quarantine Manager Reports" and click "Remove". 4. Select the option "Force removal, bypassing any checks or errors" and click OK. __________________________________________________________ TESTING YOUR INSTALLATION CONFIGURING YOUR DATABASE 1. Click Start | Programs | McAfee | Quarantine Manager | DB Management UI. NOTE: You can also configure your database by clicking "Configure Database" from the administrator log on page. You may be prompted to type your administrator credentials to access the DB Management page. 2. In the Database Configuration page, type the details such as User name, password, database name, port number, type and server. 3. Click "Test". A dialog box appears which indicates that the database is configured successfully. TESTING YOUR MCAFEE QUARANTINE MANAGER 1. After installing McAfee Quarantine Manager software, click Start | Programs | McAfee | Quarantine Manager | Administrator UI. 2. Login using the Super Admininstrator account that you specified during installation of the software. You must be able to login successfully. 3. Click "Dashboard". 4. From the "Connected McAfee Products" section, click "Test" to verify the connection between the software and the McAfee product. 5. Select "Quarantined Items ". You will find items quarantined by the SCM appliances listed in the "View Results" area. 6. Click Admin Management | Manage Domains. Provide the Domain Name and Click "Add" to create a new database to store the domain based quarantined items. NOTE: For example: If you need items to be quarantined for the domain "xyz.com", create a Domain Name with "@xyz.com" and click on "Add". 7. From the Administrator user interface, click "Quarantined Items | Spam" and select the domain name from the drop down list, to view the quarantined emails for the domain created. _________________________________________________________ UNINSTALLATION UNINSTALLATION OF MCAFEE QUARANTINE MANAGER 1. Click Start | Settings | Control Panel | Add or Remove Programs. 2. Select "McAfee Quarantine Manager", then click "Remove". 3. In the uninstall window select "Also Remove MQM data" if you wish to remove the dataBase created for storing quarantined items. NOTE: Enabling this option would delete the database permanently. UNINSTALLATION OF MYSQL FOR MCAFEE QUARANTINE MANAGER 1. Click Start | Settings | Control Panel | Add or Remove Programs. 2. Select "MySQL for McAfee Quarantine Manager", then click "Remove". UNINSTALLATION OF MCAFEE QUARANTINE MANAGER DB SUITE UTILITY 1. Click Start | Settings | Control Panel | Add or Remove Programs. 2. Select "McAfee Quarantine Manager DB Suite", then click "Remove". __________________________________________________________ KNOWN ISSUES 1. Tasks scheduled at the daylight savings transition time are not executed. 2. Groups from the second Secure Content Management appliance are not listed in the Quarantined items of the McAfee Quarantine Manager server. 3. McAfee Quarantine Manager currently supports Microsoft SQL 2005 only with Mixed mode authentication. 4. In McAfee Quarantine Manager 6.0 User Guide | Chapter 2 | System Requirements, Browsers Supported specifies "Internet Explorer 6.0 or later" instead of "Internet Explorer 6.0 or 7.0". __________________________________________________________ ADDITIONAL INFORMATION 1. When a quarantined item is released to the McAfee product, it is not deleted from the database until purging occurs. 2. While importing User Blacklist and Whitelist, user names that are not present in the software are newly created with a random password. Use the "Password Reminder" option to retrieve the new password. 3. By default, "Super Admin" and all "Domain Admin" are always managed by ePolicy Orchestrator. 4. By default, the ePolicy Orchestrator reports are not generated. WORKAROUND: To receive ePolicy Orchestrator reports, do the following on the McAfee Quarantine Manager server: a. Log on to the McAfee Quarantine Manager Administrator interface, click Settings and Diagnostics | Advanced Settings. b. Go to "ePO Related" settings in the right pane. Check the check box "Generate ePO Events". c. Set the "ePO Event(s) Generating Interval (minutes)" from 5 to 120 minutes. The default value is 10. d. Restart the "McAfee Quarantine Manager" service. 5. McAfee Quarantine Manager 6.0 does not support automatic upgrade from ePolicy Orchestrator 3.6 to 4.0. 6. To submit spam samples to McAfee labs from the administrator interface, click Settings and Diagnostics | Advanced Settings | Submission to McAfee Labs and specify the IP address of the SMTP server instead of "localhost". 7. After changing the password for an existing user in McAfee Quarantine Manager DB Suite utility, restart the Database service for changes to take effect. __________________________________________________________ DOCUMENTATION This product includes the following documentation set: - Release Notes (This ReadMe file) - Online Help High-level and detailed information accessed from the software application: Help menu and/or Help button for page-level help; right-click option for What’s This? help. - User Guide System requirements and instructions for installing and starting the software. Introduction to the product and its features; detailed instructions for configuring the software; information on deployment, recurring tasks, and operating procedures. __________________________________________________________ CONTACT INFORMATION Security Headquarters: AVERT (Anti-Virus & Vulnerability Emergency Response Team) Home Page http://www.mcafeesecurity.com/us/security/home.asp Virus Information Library http://vil.mcafeesecurity.com/ AVERT WebImmune & Submit a Virus Sample (Logon credentials required) https://www.webimmune.net/default.asp AVERT DAT Notification Service http://vil.mcafeesecurity.com/vil/join-DAT-list.asp Download Site Home Page http://www.mcafeesecurity.com/us/downloads/ Anti-Virus DAT File and Engine Updates http://www.mcafeesecurity.com/us/downloads/updates/ ftp://ftp.mcafee.com/pub/antivirus/datfiles/4.x Anti-Spam Rules File and Engine Updates ftp://ftp.mcafee.com/spamdefs/1.x/ Product Upgrades https://secure.nai.com/us/forms/downloads/upgrades/login.asp Valid grant number required (contact Customer Service) HotFix and Patch Releases - For Security Vulnerabilities (Available to the public) http://www.mcafeesecurity.com/us/downloads/updates/hotfixes.asp - For Products (ServicePortal account and McAfee Technical Support grant number required) https://mysupport.mcafee.com/products/products.asp Product End-of-Life Support http://www.mcafeesecurity.com/us/products/mcafee/end_of_life.htm SOFTWARE and hardware Technical Support Home Page http://www.mcafeesecurity.com/us/support/technical_support KnowledgeBase Search http://knowledgemap.nai.com/ McAfee Technical Support ServicePortal (Logon credentials required) https://mysupport.mcafeesecurity.com McAfee Security Alerting Service (MSAS) http://mysupport.mcafee.com/supportinfo/pvans_info.asp Customer Service US, Canada, and Latin America toll-free: Phone: +1-888-VIRUS NO or +1-888-847-8766 Monday-Friday, 8am-8pm, Central Time E-mail: https://secure.nai.com/us/forms/support/request_form.asp Web: http://www.mcafeesecurity.com/us/support/default.asp McAfee Beta Program Download Site: http://www.mcafeesecurity.com/us/downloads/beta/mcafeebetahome.htm E-mail to Submit Beta Feedback: mcafee_beta@mcafee.com Training: McAfee University http://www.mcafeesecurity.com/us/services/education/mcafee/university.htm Worldwide Offices For addresses and phone numbers of worldwide offices: http://www.mcafeesecurity.com/us/contact/home.htm _____________________________________________________ COPYRIGHT AND TRADEMARK ATTRIBUTIONS Copyright (C) 2008 McAfee, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies. TRADEMARKS ACTIVE FIREWALL, ACTIVE SECURITY, ACTIVESECURITY (AND IN KATAKANA), ACTIVESHIELD, CLEAN-UP, DESIGN (STYLIZED E), DESIGN (STYLIZED N), ENTERCEPT, EPOLICY ORCHESTRATOR, FIRST AID, FOUNDSTONE, GROUPSHIELD, GROUPSHIELD (AND IN KATAKANA), INTRUSHIELD, INTRUSION PREVENTION THROUGH INNOVATION, MCAFEE, MCAFEE (AND IN KATAKANA), MCAFEE AND DESIGN, MCAFEE.COM, MCAFEE VIRUSSCAN, NET TOOLS, NET TOOLS (AND IN KATAKANA), NETSCAN, NETSHIELD, NUTS & BOLTS, OIL CHANGE, PRIMESUPPORT, SPAMKILLER, THREATSCAN, TOTAL VIRUS DEFENSE, VIREX, VIRUS FORUM, VIRUSCAN, VIRUSSCAN, VIRUSSCAN (AND IN KATAKANA), WEBSCAN, WEBSHIELD, WEBSHIELD (AND IN KATAKANA) are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. The color red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners. _____________________________________________________ LICENSE INFORMATION LICENSE AGREEMENT NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEB SITE FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A FULL REFUND. LICENSE ATTRIBUTIONS This product includes or may include: * Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). * Cryptographic software written by Eric A. Young and software written by Tim J. Hudson. * Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL, which is distributed to someone in an executable binary format, that the source code also be made available to those users. For any such software covered under the GPL, the source code is made available on this CD. If any Free Software licenses require that McAfee provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein. * Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer. * Software originally written by Robert Nordier, Copyright (C) 1996-7 Robert Nordier. * Software written by Douglas W. Sauder. * Software developed by the Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at www.apache.org/licenses/LICENSE-2.0.txt. * International Components for Unicode ("ICU") Copyright (C) 1995-2002 International Business Machines Corporation and others. * Software developed by CrystalClear Software, Inc., Copyright (C) 2000 CrystalClear Software, Inc. * FEAD(R) Optimizer(R) technology, Copyright Netopsystems AG, Berlin, Germany. * Outside In(R) Viewer Technology (C) 1992-2001 Stellent Chicago, Inc. and/or Outside In(R) HTML Export, (C) 2001 Stellent Chicago, Inc. * Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper, (C) 1998, 1999, 2000. * Software copyrighted by Expat maintainers. * Software copyrighted by The Regents of the University of California, (C) 1996, 1989, 1998-2000. * Software copyrighted by Gunnar Ritter. * Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A., (C) 2003. * Software copyrighted by Gisle Aas. (C) 1995-2003. * Software copyrighted by Michael A. Chase, (C) 1999-2000. * Software copyrighted by Neil Winton, (C) 1995-1996. * Software copyrighted by RSA Data Security, Inc., (C) 1990-1992. * Software copyrighted by Sean M. Burke, (C) 1999, 2000. * Software copyrighted by Martijn Koster, (C) 1995. * Software copyrighted by Brad Appleton, (C) 1996-1999. * Software copyrighted by Michael G. Schwern, (C) 2001. * Software copyrighted by Graham Barr, (C) 1998. * Software copyrighted by Larry Wall and Clark Cooper, (C) 1998-2000. * Software copyrighted by Frodo Looijaard, (C) 1997. * Software copyrighted by the Python Software Foundation, Copyright (C) 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. * Software copyrighted by Beman Dawes, (C) 1994-1999, 2002. * Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek (C) 1997-2000 University of Notre Dame. * Software copyrighted by Simone Bordet & Marco Cravero, (C) 2002. * Software copyrighted by Stephen Purcell, (C) 2001. * Software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). * Software copyrighted by International Business Machines Corporation and others, (C) 1995-2003. * Software developed by the University of California, Berkeley and its contributors. * Software developed by Ralf S. Engelschall for use in the mod_ssl project (http:// www.modssl.org/). * Software copyrighted by Kevlin Henney, (C) 2000-2002. * Software copyrighted by Peter Dimov and Multi Media Ltd. (C) 2001, 2002. * Software copyrighted by David Abrahams, (C) 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. * Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, (C) 2000. * Software copyrighted by Boost.org, (C) 1999-2002. * Software copyrighted by Nicolai M. Josuttis, (C) 1999. * Software copyrighted by Jeremy Siek, (C) 1999-2001. * Software copyrighted by Daryle Walker, (C) 2001. * Software copyrighted by Chuck Allison and Jeremy Siek, (C) 2001, 2002. * Software copyrighted by Samuel Krempp, (C) 2001. See http://www.boost.org for updates, documentation, and revision history. * Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), (C) 2001, 2002. * Software copyrighted by Cadenza New Zealand Ltd., (C) 2000. * Software copyrighted by Jens Maurer, (C) 2000, 2001. * Software copyrighted by Jaakko Järvi (jaakko.jarvi@cs.utu.fi), (C) 1999, 2000. * Software copyrighted by Ronald Garcia, (C) 2002. * Software copyrighted by David Abrahams, Jeremy Siek, and Daryle Walker, (C) 1999-2001. * Software copyrighted by Stephen Cleary (shammah@voyager.net), (C) 2000. * Software copyrighted by Housemarque Oy , (C) 2001. * Software copyrighted by Paul Moore, (C) 1999. * Software copyrighted by Dr. John Maddock, (C) 1998-2002. * Software copyrighted by Greg Colvin and Beman Dawes, (C) 1998, 1999. * Software copyrighted by Peter Dimov, (C) 2001, 2002. * Software copyrighted by Jeremy Siek and John R. Bandela, (C) 2001. * Software copyrighted by Joerg Walter and Mathias Koch, (C) 2000-2002. * Software copyrighted by Carnegie Mellon University (C) 1989, 1991, 1992. * Software copyrighted by Cambridge Broadband Ltd., (C) 2001-2003. * Software copyrighted by Sparta, Inc., (C) 2003-2004. * Software copyrighted by Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, (C) 2004. * Lotus C++ API Toolkit for Notes/Domino Runtime Modules (c) Copyright IBM Corporation 2004 All Rights Reserved * Software copyrighted by Simon Josefsson, (C) 2003. * Software copyrighted by Thomas Jacob, (C) 2003-2004. * Software copyrighted by Advanced Software Engineering Limited, (C) 2004. * Software copyrighted by Todd C. Miller, (C) 1998. * Software copyrighted by The Regents of the University of California, (C) 1990, 1993, with code derived from software contributed to Berkeley by Chris Torek. DBN-002-EN V3.1.3