Support Visit mysupport.mcafee.com to find product documentation, announcements, and support.

Transcription

1 Release Notes McAfee Web Gateway version This document provides information about the McAfee Web Gateway version appliance software. You can find more information at the following locations: Help Help is built into McAfee Web Gateway. Click the Help icon in the upper right corner of the user interface. Support Visit mysupport.mcafee.com to find product documentation, announcements, and support. In this document... About this release Resolved issues Known issues Installation About this release McAfee Web Gateway version is released as a maintenance version that resolves issues present in previous versions of the product. For information on setting up and administering an appliance, see the McAfee Web Gateway Quick Start Guide, the McAfee Web Gateway Port Identification Guide, and the McAfee Web Gateway Product Guide at mysupport.mcafee.com. McAfee Web Gateway Release Notes 1

2 Resolved issues Resolved issues This release resolves the following issues (Bugzilla reference numbers are in parentheses): After scanning a file and using display of a progress page as the progress indication method, the file could only be downloaded once, not several times, within the configured time frame. (566955) A failure of the appliance core occurred after a longer overload period. (670242) A log entry was created when nothing suspicious had been found in a web object after scanning it for infections by viruses and other malware. No value was then assigned to the Virus Name log parameter, nor to the Antimalware.VirusNames property. (671635) Using the third-party Avira to scan an executable file for infections by viruses and other malware, led to a failure of the appliance core. This occurred after the file had been altered by the core process and the anti-malware engine made another attempt to access the file. (673780) The appliance performed very slowly with high system load and memory consumption. (673828, , , , , , , ) After a client request had resulted in a web cache hit, processing a further request received over the same connection led to a proxy library failure. (676904) The core process failed with term signal 11 on two appliances after a concurrent file download had been performed. (677873) Scanning a PDF file could not be completed during three days and led to a 100% CPU load. This was due to a file key that pointed to itself and caused the opener module to perform an endless loop when reading the key table. (683984) When a value was retrieved to fill the property DNS.ReverseLookup in URL filtering, several attempts were made using the IP address of a requested web site. No limit was set to the number of attempts made until the lookup succeeded. (684871) When processing a PDF file, an issue with the archive opener led to a failure of the appliance core. (688416) A failure of the appliance core occurred when the FTP-over-HTTP mode had been configured. (688464) When processing web traffic in HTTPS mode, a large amount of memory was consumed by providing server certificates from the cache, while the default cache timeout had been set to an unusually high value. This resulted in memory swapping and eventually in a failure to process any more web traffic. (689242) When processing a PDF file, an issue with the opener module led to a failure of the appliance core with term signal 11. (690586) Downloading files failed when displaying progress pages was used as the progress indication method. (690588) Access to a web site with an IP address that had been categorized as malicious was allowed by the appliance, as the URL for this web site had been categorized under Games and no forward DNS lookup had been performed for this URL. (695179). After restarting the appliance core, the default number of 25 threads were started for the anti-malware scanning process, regardless of whether a different number of threads had been configured on the user interface. (695718). When a redirection to a progress page was performed on the appliance, a memory leak occurred at the proxy module. (696206) 2 McAfee Web Gateway Release Notes

3 Known issues Known issues For information about known issues for McAfee Web Gateway version : 1 Visit mysupport.mcafee.com. 2 Log on with your user ID and password. The ServicePortal homepage appears with a welcome message at the top. If you do not have an account but have received a grant number: In the User Login section, click New User. Complete the information and follow the prompts to set up your account. If you do not have an account or grant number, contact Customer Service. 3 In the Self Service section, click Search the KnowledgeBase. The KnowledgeBase welcome page appears. 4 In the Ask a Question section, type KB72613, then click Ask. The KnowledgeBase article appears with any known issues. Installation Complete the following procedures to install maintenance version of the McAfee Web Gateway software on your appliance. Overview What is required to install version depends on the version you are currently running. If you are running a 7.x.x version, install the maintenance version as follows: Install a repository for version from a system console. Note: You need not install this repository if you are already running version 7.1 and have not installed this version fresh from CD or USB drive. Perform an update on the user interface or from a system console. For more information on these procedures, see the next sections. If you are running a 6.8.x version, you must re-image using an image of the maintenance version. Download the image from: Note: Former versions of the appliance were shipped to you with a 6.8.x software version. For more information on re-imaging the appliance, see the McAfee Web Gateway Appliances Installation and Configuration Guide. McAfee Web Gateway Release Notes 3

4 Installation Install the repository [conditional] If the following applies, you need to install a repository before performing the update that installs version : You are running a 7.x.x version other than version 7.1. You are running version 7.1, but have installed it fresh from CD or USB drive. In both cases, proceed as follows: 1 Log on the the appliance from a system console, using SSH. 2 Run the following command: yum install yumconf mwg Note: It is due to a known issue for version 7.1 (Bugzilla number ) that you need to proceed in this way if you have installed version 7.1 fresh from CD or USB drive. Remove a beta version [conditional] If you have been beta-testing a 7.x.x version, you need to remove the beta version before you can install the new version. Note: Make sure you have another repository configuration installed before you remove the beta version. To remove the beta version: 1 Log on to the appliance from a system console, using SSH. 2 Run the following two commands: yum clean all yum remove yumconf-beta Perform an update You can perform an update on the user interface or from a system console. Update on the user interface To update on the user interface: 1 Go to Configuration Appliances. 2 On the appliances tree, select the appliance you want to update. The Appliance toolbar appears on the upper right side of the tab. 3 Click Update Appliance Software. The new version is installed on your appliance. 4 Click Reboot to complete the installation. Update from a system console To update from a system console: 1 Log on to the appliance using SSH. 2 Run the following commands: yum upgrade yum yumconf\* yum upgrade The new version is installed on your appliance. 3 Run the following command to complete the installation: reboot 4 McAfee Web Gateway Release Notes

5 Installation For support information, visit mysupport.mcafee.com. Copyright 2011 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 A00 5 McAfee Web Gateway Release Notes