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. Resolved issues This release resolves the following issues (Bugzilla reference numbers are in parentheses): For several properties used in URL filtering, the type these properties had when used in normal rules differed from the one they had in logging rules. The value was true or false in normal rules, but 0 in logging rules. (660126) A regular expression was accepted when entered on the user interface, but failed to work when actually used in a rule. The regular expression included an alternative term where no value was specified for the second part of the alternative. (663817) McAfee Web Gateway Release Notes 1

2 Resolved issues The FTP command Print Working Directory was not executed correctly when a folder name contained Chinese characters. (665267) In a central management configuration, the coordinator module on a master node had to wait for a connection to an unreponsive remote node, which led to an impact on performance, for example, when loading the user interface. (665884) After a session had been blocked due to quota expiration, clicking the button to continue with the session failed. The Microsoft Internet Explorer 8 was used on Windows 7 during this session. (665886) Using a rule to enable the SafeSearchEnforcer lead only to enabling the SafeSearch function within Google Search, but not within Yahoo Search. (667042) When upgrading from version of the appliance to 7.1, larger configuration settings, for example, a proxy configuration with more than 15 proxy ports, were not completely implemented, which led also to the sysconf daemon not properly loading. (667265) Web pages were not loading and CPU usage by the core module went up due to an endless loop, which was caused by a problem of the DNS cache with handling IP addresses. (667313, ) The core module failed when the unpacking of an archive led to an endless loop. (667402) After appropriate feedback could not be retrieved on some appliances that had gone out of operation, the feedback or the core module process could not be terminated due to a failure in the appliance kernel. This was caused by a problem with handling transaction numbers. (667426, , ) The appliance stopped processing web traffic and a high number of connections to the proxy module entered the close_wait state due to a problem with handling requests for a particular file type. (669076) After sending a request to a next-hop proxy and receiving the response that the requested host could not be resolved, the appliance kept on sending the same request again and again. (669174) When some long runnning tunneled SSL connections were closed, this led to a failure of the core module and the sending of term signal 11. (669584) A restriction that is required on an appliance when running in FIPS-compliant mode, prevented certificate authorities with a key length of less than 2048 bit from being accepted in standard mode. (669661) When the SafeSearchEnforcer was enabled, requests that were forwarded to Google servers contained cookies with additions in the wrong fields. After this had happened several times, Google blocked the user who had originally sent the requests. (669889) When a client sent a POST request for a chunk-encoded body, the appliance refused to accept the request after the client had forwarded the body. (670114) Although a whitelist entry had been created for a web site that provides Microsoft Windows updates, this site was not whitelisted, which could have led to additional load on the engines used in virus and anti-malware filtering. (670852) Several PDF files and a.rar archive file were processed for more than 40 hours on the appliance while CPU usage remained the same all the time. (671063) The core module failed after receiving a request from a client for a web object that had already been cached on the appliance. The object still needed to be validated, but the client did not keep the connection persistent. (671344) Unpacking a gzip encoded object received from a web server showed that an incorrect check sum had been sent with the object. Otherwise, the unpacking could successfully be completed. The appliance then sent an error message to the client instead of ignoring the check sum error and forwarding the object. (671962) Two appliances sent term signal 7 and stopped working after attempting to process a particular PDF file. (672396) 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 KB71779, 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