Initial prototype
This commit is contained in:
@@ -0,0 +1,191 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.2
|
||||
---
|
||||
|
||||
## GPC-22087
|
||||
|
||||
Fixed an issue where the GlobalProtect app was unable to validate the certificate from OCSP.
|
||||
|
||||
## GPC-22080
|
||||
|
||||
Fixed an issue where the OCSP requests were being rejected by the OCSP responder with a HTTP 400 Bad Request error due to the absence of the Host header in the OCSP request.
|
||||
|
||||
## GPC-21938
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.3.x was installed on devices running macOS, the HIP check failed to detect ESET Endpoint Security version 8.
|
||||
|
||||
## GPC-21918
|
||||
|
||||
Fixed an issue where, when the patch management category was excluded for HIP checks, HIP checks were still happening for missing patches which consumed CPU resources on users' machine.
|
||||
|
||||
## GPC-21838
|
||||
|
||||
Fixed an issue in which the GlobalProtect app, when installed on Windows devices, caused a duplicate page to open in the system default browser (Chrome) when the user clicked the hyperlink on the Welcome page with fedmandate on the embedded browser.
|
||||
|
||||
## GPC-21836
|
||||
|
||||
Fixed an issue in GlobalProtect 6.3.1 for macOS where the Refresh Connection option was missing during the Connecting state, specifically for users who upgraded from version 6.3.0.
|
||||
|
||||
## GPC-21778
|
||||
|
||||
Fixed an issue where the GlobalProtect IPSec tunnel got disconnected on GlobalProtect app version 6.2.5 when gpupdate /force command was used to update policy.
|
||||
|
||||
## GPC-21774
|
||||
|
||||
Fixed an issue where the GlobalProtect ARM64 installers for 6.2.5 version did not display the Digital Signatures tab.
|
||||
|
||||
## GPC-21771
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Malware Definition Date for Trend Micro Deep Security Agent, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21733
|
||||
|
||||
Fixed an issue where all the added portals got deleted from the portal list except the connected portal when the GlobalProtect app was upgraded from version 6.2.4 to 6.2.5-788. Users had to manually add them again to resolve the issue.
|
||||
|
||||
## GPC-21604
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS and were connected to the internal gateway, the app did not display the Disconnect option under Settings.
|
||||
|
||||
## GPC-21571
|
||||
|
||||
Fixed an issue where the hyperlink in HIP notification opened up in Webview2 instead of the default browser.
|
||||
|
||||
## GPC-21565
|
||||
|
||||
Fixed an issue where the SAML embedded browser did not remember the username after sign-out, even when the user had selected the check box Remember Me on the SAML embedded browser.
|
||||
|
||||
## GPC-21542
|
||||
|
||||
Fixed an issue where GlobalProtect got stuck in connecting and failed the connection after some time.
|
||||
|
||||
## GPC-21443
|
||||
|
||||
Fixed an issue where GlobalProtect crashed when the PanGPS service was stopped.
|
||||
|
||||
## GPC-21414
|
||||
|
||||
Fixed an issue where the SAML authentication page would occasionally fail to appear due to the usage of a previous SAML pre-login cookie.
|
||||
|
||||
## GPC-21399
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the HIP check for the built-in firewall shows N/A incorrectly.
|
||||
|
||||
The value should be either Yes or No.
|
||||
|
||||
## GPC-21370
|
||||
|
||||
Fixed an issue where the HIP check could not detect Trellix Firewall Status, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21332
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Real Time Protection status for Avast and XProtect, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21320
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Kaspersky Endpoint Security antimalware application which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21301
|
||||
|
||||
Fixed an issue where, when the user upgraded the GlobalProtect app version to 6.2.4 with SAML authentication, users were unable to connect to GlobalProtect intermittently when Enforcer is enabled.
|
||||
|
||||
## GPC-21247
|
||||
|
||||
Fixed an issue where GlobalProtect HIP set the Filevault encryption status to unencrypted on macOS running devices, which denied access to the end-point machines.
|
||||
|
||||
## GPC-21222
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected the Real Time Protection Status and Last Full Scan for Avast application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21206
|
||||
|
||||
Fixed an issue where the GlobalProtect service exited when the user logs off or put the computer in sleep mode.
|
||||
|
||||
## GPC-21174
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Real time protection status for Acronis Cyber Protection Agent, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21130
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect app failed to reconnect and continued to stay in the Connecting state after the device woke up from Modern Standby mode.
|
||||
|
||||
## GPC-21106
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Real Time Protection status for Malwarebytes antimalware application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21043
|
||||
|
||||
Fixed an issue where the GlobalProtect app got stuck in connecting stage after authentication when the app was upgraded to 6.2.4 version.
|
||||
|
||||
## GPC-20983
|
||||
|
||||
Fixed an issue where the GlobalProtect app was installed on devices running macOS, the GlobalProtect got stuck in Connecting state when the device woke up from sleep mode.
|
||||
|
||||
## GPC-20967
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed with the Conditional Connect method, users had to click the Connect button twice to connect to an external gateway after a system reboot.
|
||||
|
||||
## GPC-20943
|
||||
|
||||
Fixed an issue where the GlobalProtect enforcer blocked DHCP packets.
|
||||
|
||||
## GPC-20838
|
||||
|
||||
Fixed an issue where the HIP report was not completed within the allowed time.
|
||||
|
||||
## GPC-20807
|
||||
|
||||
Fixed an issue where the HIP report for Symantec Encryption Desktop shows the encryption state as unencrypted.
|
||||
|
||||
## GPC-20779
|
||||
|
||||
Fixed an issue where Windows regional settings were not respected by Webview 2 on SAML embedded browser resulting in regional language(French, German, Chinese, Spanish, and Japanese) not loading properly in embedded browser.
|
||||
|
||||
## GPC-20700
|
||||
|
||||
Fixed an issue where macOS users had to enter the SAML username and password each time they refreshed or rebooted their computer. This issue occurred more frequently when they used Safari as the default browser or used the embedded browser.
|
||||
|
||||
## GPC-20674
|
||||
|
||||
Fixed an issue where all GlobalProtect portals except for the currently connected portal were deleted during the upgrade from 6.2.2 to 6.2.3 or from 6.2.3 to 6.3.0.
|
||||
|
||||
## GPC-20492
|
||||
|
||||
Fixed an issue where the PanGPS process crashed due to exception code 0xC0000374.
|
||||
|
||||
## GPC-20466
|
||||
|
||||
Fixed an issue where the tunnel gets broken during modern standby when using Enforce GlobalProtect for Network Access and the enforcer gets re-enabled only after the user resumes working on the computer.
|
||||
|
||||
## GPC-20441
|
||||
|
||||
Fixed an issue where HIP reports are sometimes not available on the firewall for newly connected users.
|
||||
|
||||
## GPC-20322
|
||||
|
||||
Fixed an issue where users were unable to install GlobalProtect 6.2 on windows 11 ARM64 devices.
|
||||
|
||||
## GPC-20191
|
||||
|
||||
Fixed an issue where the PanGPA executable version 6.1.2.83 did not work as expected on Windows devices.
|
||||
|
||||
## GPC-20168
|
||||
|
||||
Fixed an issue where it was possible to do a privilege escalation and\or login bypass when using a 3rd party credential provider with GlobalProtect.
|
||||
|
||||
## GPC-18943
|
||||
|
||||
Fixed an issue where when Endpoint Traffic enforcement feature was enabled, certain traffic was going through the physical adapter and not getting blocked as per the rules set.
|
||||
|
||||
## GPC-18695
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.0.7 was installed on devices running macOS, the "Allow with Passcode option did not work as expected when the user tried to disable the GlobalProtect app with the configured passcode.
|
||||
|
||||
## GPC-18671
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect macOS install package created an unused /Library/Application folder.
|
||||
|
||||
## GPC-18452
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the app did not start right away after a system reboot.
|
||||
Reference in New Issue
Block a user