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 provided as a main release. It is 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): Issues with headers and other protocol-related issues In requests sent by a client to the appliance, the URL path was modified when it contained multiple forward slashes, which led to an unknown type response from the web server. (688729) User information provided in authentication headers that were added to requests by an ISA chaining plugin was lost when tunneling was performed during SSL scanning on an appliance. (696873) When the NTLM authentication method was used on an appliance, a response sent to a client to request header information wrongly included a body. This led to a failure when trying to retrieve updated information. (718582) Processing patches for sony playstation pages with incorrect header information lead to a decrease in performance. (730007) Issues with resolving domain names When the Response.StatusCode property was used in a block message to the user, its value was always 0 if HTTP status code 502 had been sent to the client after a failed DNS lookup. However, when used in a logging rule for the access log, the property had the correct value for this status code. (697530) When trying to resolve a domain name, the response from the DNS server led to querying other servers in an endless loop. (726966) Authentication issues The Authentication.Realm property was not filled with values when HTTPS requests were received on the appliance and SSL scanning was enabled. (689609) An alert displayed on the dashboard still referred to an NTLM-Agent module that no longer existed in the appliance configuration. (695113) Logon to the user interface was not possible after a timeout due to an endless loop that had occurred when trying to authenticate an administrator. (703962) When using the NTLM-Agent method, an attempt to authenticate after authentication had already been performed successfully, led to closing the connection to the client and sending an error message. (720778) Authentication under the NTLM-Agent method with the NTLM cache enabled failed several times (721575) Issues with opening files When processing a zipped file, an issue with the archive handler led to a core failure. (693771) When trying to open a document that was UTF-32 encoded and convert it into UTF-8, invalid characters inside the document caused the HTML Opener to reserve more memory than was available, which led to a failure of the core process with term signal 6. (704617) Processing large files in UTF encoding caused problems with an internal buffer. This led to a failure of the HTLM Opener and eventually of the core process, which closed down sending term signal 11. (712563) Opening zipped files that no file names were provided for led to a failure of the core process with term signal 11. (726453) 2 McAfee Web Gateway Release Notes

3 Known issues Issues with access permissions Accessing a list by clicking its name in a rule failed to work although the administrator role included permissions for rules and lists. (724103) After a particular type of files had been edited by a user with limited permissions, root user permissions were unintentionally given to the original user. (728651) Logging issues Log lines on request processing could not be imported by Web Reporter because the User Agent and Protocol parameters were not logged on the appliance. (693229) A meaningless message on truncating unsigned values was logged several times when the syslog function was enabled. (702988) Information included in an authentication request, for example, a user name, was missing in a log entry for the request when this information appeared before a forward slash because this character had also been used as a domain separator. (703172) Pushing log files was claimed to have been completed successfully while a TCP dump showed no files had been pushed. (726987) For requests sent under the HTTPS protocol, the request method was not logged when a blocked domain was requested or the domain name could not be resolved. (729780) Other issues When processing the proxy.pac and wpad.dat auto-configuration files, connections stayed open too long. This caused redirects to fail, due to a limit in the number of redirects that could be performed in the available time. (688018) Load balancing on two appliances worked in general, but load was unevenly distributed. (704306) In a High Availability configuration with a director and a scanning node, the scanning node initiated the end of the communication unexpectedly after several GET requests had been received from a client and processed properly. (715940) Timezone information was outdated after changes in several countries. (731153) Media type filtering with data trickling enabled caused the core process to fail with term signal 11. (734098) When credentials submitted for a request exceeded a particular size, a failure of the user interface occurred due to insufficient memory. (725575) Filtering POST requests that involved an ASPX file led to a failure of the core process with term signal 11 (725683) Known issues For known issues in this product release, refer to KnowledgeBase article KB McAfee Web Gateway Release Notes 3

4 Installation Installation Complete the following procedures to install 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. Note: If you have been beta-testing an older version, you need to remove this version first, see Remove a beta version. If you are running version or a lower 7.x.x.x version, you can update to the new version, see Perform an update. If you are running a 6.8.x.x or 6.9.x.x version, you must re-image using an image of the new version. Download the image from: For more information on re-imaging the appliance, see the McAfee Web Gateway Appliances Installation and Configuration Guide. Remove a beta version To remove a beta version before installing the new version: 1 Make sure you have another repository configuration installed. 2 Log on to the appliance from a system console, using SSH. 3 Run the following two commands: yum clean all yum remove yumconf-beta The beta version is removed from your appliance. 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. 4 McAfee Web Gateway Release Notes

5 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 For support information, visit mysupport.mcafee.com. Copyright 2012 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