McAfee Web Gateway

Transcription

1 Release Notes Revision A McAfee Web Gateway Contents About this release Resolved issues Installation instructions Known issues Find product documentation About this release This document contains important information about the current release. We strongly recommend that you read the entire document. McAfee Web Gateway (Web Gateway), version , is provided as a controlled release. It is a maintenance version that resolves issues present in previous versions. Resolved issues These issues are resolved in this release of the product. Bugzilla reference numbers are in parentheses. 1

2 Network communication When an IFP proxy had been configured on Web Gateway, processing requests failed several times, as not only the requested URLs were submitted, which would have been compliant with the IFP protocol, but complete request headers. ( ) The core process failed with term signal 11 due to a problem with a flag that had incorrectly not been reset after handling a long-running connections error. ( ) Port 8443 was no longer available for listening to incoming requests because it was occupied by an internal Web Gateway service. ( ) Web filtering When quota rules were synchronized in a Central Management cluster, the core process failed on one appliance with term signal 6. (965782) Real-time streaming data could not be processed due to a problem with the Helix proxy that had been enabled on Web Gateway for this purpose. (968670) Three new URL-related properties could not be saved and used in rules, as they worked only when embedded in error templates. ( ) The dashboard did not show the update status of the McAfee Anti-Malware engine on the System Summary table. ( ) The user interface was not accessible and an error message stated that the internal configurator could not be started, which was caused by a problem with an invalid list entry. ( ) Error messages about the state of the Reporting.URL.Categories property were created, although the value of the URL.Categories property was already known and should have been used to determine the value of the former property. ( ) Data for an update could not be downloaded from the web over a next-hop proxy when the Verify SSL Tunnel setting was enabled, as this setting triggered some requests that could not be sent over a next-hop proxy. ( ) When the URL.SmartMatch property was used to find out whether entries in a list matched parts of requested URLs, a list entry beginning with a dash would match any URL. ( ) After receiving an ICAP request without a host header on Web Gateway, an internal URL filtering error occurred when the URL.Categories property was processed. ( ) The URL filtering module sent a query to a DNS server that included a port number, which caused the lookup to fail. ( ) A request was blocked in SSL-secured communication when the certificate chain was erroneously taken to contain an expired certificate, as an intermediate certificate authority used a time format that could not be processed correctly. ( ) Download of an Adobe Acrobat archive file was blocked because it was falsely suspected to be malware after scanning. ( ) Miscellaneous When text was searched to process rules for Data Loss Prevention (DLP), words containing particular Russian letters were not supported due to an issue with character conversion. (985776) Entries in the PDStorage user map were not correctly removed when their lifetime was exceeded, nor when the PDStorage.Cleanup event was used in a rule. ( ) The table for configuring static routes disappeared and connections were dissolved after 208 entries had been inserted. ( ) 2

3 The core process failed with term signal 11 due to a file reading problem. ( ) Wrong incident IDs were shown on the dashboard for successful and failed scheduled jobs. ( ) When a scheduled job could not download a new version of a proxy.pac file due to a connection issue, the existing version of the file was overwritten with an empty file. ( ) The explaining text for SNMP monitoring that is provided on Web Gateway did not mention a severity level 6, although an SNMP trap with this level was shown on the managing system. ( ) After upgrading to a new version of Web Gateway, some alerts were incorrectly repeated on the dashboard many times. ( ) The core process failed with term signal 11 due to an internal problem, which occurred when maps were written for rule tracing. ( ) Installation instructions The requirements for installing Web Gateway, version on an appliance depend on the version you are currently running. When running version or an earlier 7.5.x, 7.4.x, or 7.3.x version, you can upgrade to the new version after activating a repository. See Upgrade from 7.3.x or later. When running a 7.2.x or any earlier 7.x version: Create a configuration backup. Use the options provided under Troubleshooting Backup/Restore on the user interface to create the backup. Upgrade to the new version. See Upgrade from 7.2.x or earlier 7.x. The upgrade process includes a major upgrade of the operating system. It will take several steps and more time than usual. If the upgrade process fails or is interrupted, you can re-image the appliance using an image of the new version and install the configuration backup. Alternatively, you can: Create a configuration backup. Re-image the appliance using an image of the new version and install the configuration backup. When running a 6.8.x or 6.9.x version, you must re-image the appliance using an image of the new version. Download an image of the new version from the download page of the McAfee Content & Cloud Security Portal at For more information on re-imaging, see the McAfee Web Gateway Installation Guide. 3

4 Upgrade from 7.3.x or later When running a 7.5.x, 7.4.x, or 7.3.x version, you can upgrade to the new version after activating a repository. You can perform the upgrade on the user interface or from a system console. Activate the repository Activate the repository for the new version before upgrading on the user interface or from a system console. You can activate the repository from a local system console, which is directly connected to an appliance, or work remotely, using SSH. 1 Log on to the appliance you want to perform the upgrade on. 2 Run the following command: mwg-switch-repo You can now upgrade to the new version on the user interface or from a system console. Upgrade on the user interface You can work with the options of the user interface to perform the upgrade. 1 Select Configuration Appliances. 2 On the appliances tree, select the appliance you want to perform the upgrade on. The appliance toolbar appears on the upper right of the tab. 3 Click Update Appliance Software. The upgrade to the new version is performed. The upgrade process also logs you off from the user interface. 4 When a message informs you that the upgrade has completed, proceed as follows: a Log on to the user interface again. b c Select Configuration Appliances, then select your appliance. On the appliance toolbar, click Reboot. When the restart has completed, you can log on to the user interface again and start working with the new version. 4

5 Upgrade from a system console You can upgrade from a local system console, which is directly connected to an appliance, or remotely, using SSH. 1 Log on to the appliance you want to perform the upgrade on. 2 Run the following two commands: yum upgrade yum yum upgrade The upgrade to the new version is performed. 3 When a message informs you that the upgrade has completed, run the following command: reboot When the restart has completed, a logon prompt appears. You can now log on to the user interface and start working with the new version. Upgrade from 7.2.x or earlier 7.x When running a 7.2.x version or any earlier 7.x version, use a system console to upgrade to the new version. You can use a local system console, which is immediately connected to an appliance, or work remotely, using SSH. 1 Log on to the appliance you want to perform the upgrade on. 2 Run the following two commands: yum upgrade yum yumconf\* mwg-dist-upgrade The upgrade to the new version is performed in two phases. After each phase, the appliance restarts automatically. 5

6 3 Proceed in one of the following ways to complete the installation: If you are using a local system console: When the second restart has completed, a logon prompt appears. You can now log on to the user interface and start working with the new version. If you are using SSH: When the appliance restarts after the first upgrade phase, you are disconnected and the second upgrade phase begins. After this phase has completed, including the automatic restart, you can log on to the user interface and start working with the new version. If you log on before the second upgrade phase has completed, a message states that this phase is still in progress. When the appliance restarts at the end of this phase, you are disconnected again. Then you need to log on again to be able to work with the new version. You can also run the following command to view messages about the upgrade progress: tail -F /opt/mwg/log/update/mlos2.upgrade.log When you see that the upgrade has completed, press Ctrl+C to stop the monitoring process. You can now log on to the user interface and start working with the new version. Known issues For a list of known issues in this product release, see this McAfee Knowledge Base article: KB Find product documentation After a product is released, information about the product is entered into the McAfee online Knowledge Center. 1 Go to the Knowledge Center tab of the McAfee ServicePortal at 2 In the Support Content pane: Click Product Documentation to find user documentation. Click Technical Articles to find KnowledgeBase articles. 3 Select Do not clear my filters. 4 Enter a product, select a version, then click Search to display a list of documents. 6

7 Product documentation Every McAfee product has a comprehensive set of documentation. For Web Gateway, this includes the following: McAfee Web Gateway Product Guide Describes the features and capabilities of Web Gateway, providing an overview of the product, as well as detailed instructions on how to configure and maintain it. McAfee Web Gateway Installation Guide Describes how to set up Web Gateway, as well as several devices that can be run with the product. McAfee Web Gateway Quick Start Guide Describes high-level steps for setting up a Web Gateway version that is shipped as pre-installed appliance software on a hardware platform. This document is shipped in printed format with the pre-installed software and the hardware. Web Gateway, version is not provided as pre-installed software. Copyright 2014 McAfee, Inc. Intel and the Intel logo are trademarks/registered trademarks of Intel Corporation. McAfee and the McAfee logo are trademarks/ registered trademarks of McAfee, Inc. Other names and brands may be claimed as the property of others. A00