Hotfix 06
This hotfix rolls up Hotfix 06, which includes the following changes.
Issues resolved
This hotfix resolves the following issues:
- The Content Gateway proxy added approximately 40 - 100 milliseconds of latency to the first request on a connection that followed an idle gap. Small or intermittent traffic, such as periodic application health checks, was affected. Continuous traffic was not affected.
- The Advanced Malware Detection (AMD) file-sandbox component (ssbc) failed to connect to the cloud sandbox in environments where the Content Gateway proxy enforced authentication on the sandbox path. The CONNECT request returned HTTP 407, retried three times, raised alarm 3000, and the ANT process aborted into a restart loop, resulting in loss of file sandboxing.
- The product health and usage telemetry feature introduced in Hotfix 05 used outdated configuration values.
New features
PolicyEngine 10.4.0 upgrade with updated OCR capabilities
This hotfix upgrades PolicyEngine to version 10.4.0, which includes updated optical character recognition (OCR) capabilities.
Note:
- If Hotfix 04 is not installed, installing this hotfix upgrades PolicyEngine directly from version 10.3.0 to the 10.4.0 (Cumulative) build, which includes the OCR improvements. Uninstalling this hotfix rolls back PolicyEngine to version 10.3.0.
- If Hotfix 04 is installed, PolicyEngine is already running the 10.4.0 (Baseline) build. Installing this hotfix updates PolicyEngine to the 10.4.0 (Cumulative) build, which includes the OCR improvements, and the version number stays the same. Uninstalling this hotfix rolls back PolicyEngine to the 10.4.0 (Baseline) build installed by Hotfix 04.
- If Data Loss Prevention (DLP) is installed but Web Security is not installed, and Web DLP is not enabled in Content Gateway, DSS registration is not performed, by design. The hotfix installation still completes successfully. If registration is required, enable Web DLP to perform it.
- In any other case where DSS registration fails, the hotfix installation still completes successfully and an alarm is displayed in Content Gateway Manager. To resolve this, perform the registration manually by using the following command:
<WCG_DIR>/bin/dss_register <DLP_IP> <DLP_Username> <DLP_Password>