Hotfix 05

This hotfix rolls up Hotfix 05, which includes the following changes.

Issues resolved

This hotfix resolves the following issues:

  • Files greater than 2 GB failed to upload through the SOCKS proxy.
  • Outdated Trellix update files accumulated over time, causing disk space exhaustion due to the lack of automatic cleanup.
  • The SMBAdmin script incorrectly created the Load Balancer AES keytabs.

New features

Allow disabling NTLMv1 authentication

The Content Gateway proxy can now reject New Technology LAN Manager v1 (NTLMv1) authentication while continuing to accept NTLMv2, Kerberos, and other protocols. This applies to both Legacy NTLM and Integrated Windows Authentication (IWA).

A new configuration parameter has been added in records.config:

proxy.config.ntlm.disable_ntlmv1
  • 0 (default): NTLMv1 blocking is disabled; existing behavior is preserved.
  • 1: Enables blocking of NTLMv1 authentication.
Note: Rejected clients receive an HTTP page explaining that NTLMv2 is required. For HTTPS requests, the browser may show ERR_TUNNEL_CONNECTION_FAILED. This is expected browser behavior, not a proxy error, and can be confirmed by testing an HTTP-only site, which displays the custom error page.

Serviceability enhancement: product health and usage telemetry

This hotfix introduces product health and usage telemetry within Forcepoint Web Security. The product periodically transmits system-level health and configuration data to Forcepoint to support improved serviceability of the platform. No personal data, user data, or customer content is collected or transmitted. For details about the data collected and its purpose, see the SWG On-Premises Product Health and Usage Telemetry Knowledge Base article.