Add GP 6.1 addressed issues
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-Linux
|
||||
version: 6.1.1
|
||||
---
|
||||
|
||||
## GPC-16324
|
||||
|
||||
Fixed an issue where Endpoint Traffic Policy Enforcement dropped IPv6 ICMP neighbor discovery packets causing the IPv6 tunnel to drop.
|
||||
|
||||
## GPC-16029
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, users were prompted for certificate selection even when the Extended Key Usage OID for Client Certificate' was configured in the App Configurations area of the GlobalProtect portal configuration.
|
||||
|
||||
## GPC-15989
|
||||
|
||||
Fixed an issue where, when the Default System Browser is used for SAML, the GlobalProtect app kept displaying Connecting when connected to an internal gateway.
|
||||
|
||||
## GPC-15994
|
||||
|
||||
Fixed an issue where Endpoint Traffic Policy Enforcement interaction with Windows Filter Platform (WFP) and third-party vendors caused intermittent user tunnel drops.
|
||||
|
||||
## GPC-15972
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect the Real-Time Protection status correctly for the CrowdStrike Falcon application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-15834
|
||||
|
||||
Fixed an issue where the GlobalProtect app got disconnected after HIP check.
|
||||
|
||||
## GPC-15677
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on macOS, users were prompted for login when the app was installed using the property list (plist) with On-Demand connect method.
|
||||
|
||||
## GPC-15991
|
||||
|
||||
Fixed an issue where the GlobalProtect app installer was displaying the wrong Palo Alto Networks logo.
|
||||
|
||||
## GPC-15534
|
||||
|
||||
Fixed an issue where the proxy credential pop-up window did not show when connecting to the GlobalProtect portal after upgrading the GlobalProtect app to version 5.2.5 and above.
|
||||
|
||||
## GPC-15167
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was installed on devices running macOS, the GlobalProtect enforcer continued to block network access even after connecting to the internal gateway.
|
||||
@@ -0,0 +1,205 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-Linux
|
||||
version: 6.1.3
|
||||
---
|
||||
|
||||
## GPC-19336
|
||||
|
||||
Fixed an issue where the ADEM portal did not display user information such as User-ID when the ADEM portal was changed from on-premises to Prisma Access.
|
||||
|
||||
## GPC-18964
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS and the user upgraded the GlobalProtect version from 6.0.5 to 6.2.1, the app got disconnected after 10 minutes.
|
||||
|
||||
## GPC-18913
|
||||
|
||||
Fixed an issue where the GlobalProtect app changed the connection status to Not Connected even though the app was connected to the internal gateway.
|
||||
|
||||
## GPC-18907
|
||||
|
||||
Fixed an issue where the GlobalProtect app on macOS endpoints did not query the secondary DNS (when primary DNS is not responding) when the domain was part of the exclude domain list (both network and DNS).
|
||||
|
||||
## GPC-18822
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the device was reset using the Microsoft Recovery tool, the GlobalProtect app was not properly displayed.
|
||||
|
||||
## GPC-18788
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee Total Protection as an anti-malware application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18733
|
||||
|
||||
Fixed an issue where the hyperlinks with the URLs containing the = character in the HIP notification message did not work as expected and the page did not open when the user clicked the URL.
|
||||
|
||||
## GPC-18728
|
||||
|
||||
Fixed an issue where the I Agree option on the GlobalProtect app Welcome page did not work as expected when the user selected the option using a keyboard.
|
||||
|
||||
## GPC-18720
|
||||
|
||||
Fixed an issue where the GlobalProtect app became unresponsive when the user clicked the ESC button during authentication using a hard token.
|
||||
|
||||
## GPC-18599
|
||||
|
||||
Fixed an issue where Linux endpoints could not resolve FQDNs when the GlobalProtect tunnel was connected because the host stopped listening to UDP/53 on the loopback IP address.
|
||||
|
||||
## GPC-18598
|
||||
|
||||
Fixed an issue where the GlobalProtect SSO tile was selected instead of the Windows Password tile in the Windows Login screen even though the registry key MakeGPCPDefault was set to No.
|
||||
|
||||
## GPC-18594
|
||||
|
||||
Fixed an issue where the GlobalProtect app was unable to send HIP reports when the app was connected using IPv6 address.
|
||||
|
||||
## GPC-18566
|
||||
|
||||
Fixed an issue where the GlobalProtect app incorrectly displayed the gateway as internal when it was connected to an external gateway.
|
||||
|
||||
## GPC-18528
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected the version for KES 12 (Kaspersky Endpoint Security), which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18512
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running Ubuntu 22.04 or REHL 9.1, the app got disconnected periodically.
|
||||
|
||||
## GPC-18471
|
||||
|
||||
Fixed an issue where, when multiple wa_3rd_party_host_64.exe processes persisted even after the HIP check was performed, the GlobalProtect app stopped working.
|
||||
|
||||
## GPC-18426
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was configured with the 'Disable GlobalProtect option set to Allow With Ticket, the app did not display the correct Disable Duration time.
|
||||
|
||||
## GPC-18383
|
||||
|
||||
Fixed an issue where the GlobalProtect app failed to connect on Windows 11 endpoints with error Could not connect to the GlobalProtect service.
|
||||
|
||||
## GPC-18379
|
||||
|
||||
Fixed an issue where, when the IP address type was set to IPv4 and IPv6, the GlobalProtect app could connect only to the manual gateway instead of connecting to the best available gateway.
|
||||
|
||||
## GPC-18367
|
||||
|
||||
Fixed an issue where, when pre-logon was configured for the GlobalProtect app, the GlobalProtect portal displayed the FQDN or IP address of the gateway and not the gateway name. With this fix, the portal displays the gateway name instead of FQDN or IP address.
|
||||
|
||||
## GPC-18336
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app got automatically connected after a system reboot even though the connection method configured was On-Demand.
|
||||
|
||||
## GPC-18318
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was connected to the internal gateway, the app displayed the message : Connected - Inter.... instead of Connected.
|
||||
|
||||
## GPC-18251
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe as an anti-malware application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18230
|
||||
|
||||
Fixed an issue where, when the user entered credentials during SAML authentication after the set internal login timer, the app displayed an authentication failed message without providing the reason. The Retry button on the app web interface did not work properly when using an embedded browser for authentication. The Retry button was not fully visible on the embedded browser.
|
||||
|
||||
## GPC-18223
|
||||
|
||||
Fixed an issue where GlobalProtect experienced a prolonged connection time when IPv6 was disabled on Windows devices.
|
||||
|
||||
## GPC-18200
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe as an antivirus application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18173
|
||||
|
||||
Fixed an issue where the vertical scroll bar on the GlobalProtect app web interface did not work properly when users tried to select the certificate from the drop-down.
|
||||
|
||||
## GPC-18171
|
||||
|
||||
Fixed an issue where users were unable to select the external gateway manually when connected to the internal network. The GlobalProtect stayed in Connecting state and users had to manually disconnect the connection and connect to the internal network to exit the Connecting state.
|
||||
|
||||
## GPC-18167
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed the Prisma Access gateways that were not set for manual selection.
|
||||
|
||||
## GPC-18157
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed the Credential Provider language in English when the system language was German.
|
||||
|
||||
## GPC-18155
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices, the app displayed the text in an incorrect format and the users were unable to read the information displayed on the app.
|
||||
|
||||
## GPC-18146
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the GlobalProtect HIP check did not detect the correct details for Cortex XDR, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18135
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect HIP check detected the WithSecure antivirus software as XProtect, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18107
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe – Internet Security, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18092
|
||||
|
||||
Fixed an issue where GlobalProtect connected to an internal gateway got automatically disconnected after a certain period of time.
|
||||
|
||||
## GPC-18060
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee Total Protection, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18039
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect the Definition Date correctly for the CrowdStrike application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-17914
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on macOS endpoints and split tunnel was configured based on the application, the Zoom app got disconnected intermittently.
|
||||
|
||||
## GPC-17896
|
||||
|
||||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: Cannot Verify Server Certificate of Gateway.
|
||||
|
||||
## GPC-17640
|
||||
|
||||
Fixed an issue where, when the upgrade script update_tmp.bat was used, the error message did not display the correct exit timeout for the PanGPS uninstall process.
|
||||
|
||||
## GPC-17518
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed the status as Connected-Internal even when the app was not connected.
|
||||
|
||||
## GPC-17492
|
||||
|
||||
Fixed an issue where, when the traffic enforcer setting was applied for pre-logon and the GlobalProtect app was disconnected, the new user setting did not get updated and the pre-logon setting was still applicable.
|
||||
|
||||
## GPC-17204
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the certificate information was not accessible even though the GlobalProtect app had full access to the certificate store.
|
||||
|
||||
## GPC-17161
|
||||
|
||||
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-17001
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running on macOS, the app did not display the Connect button and Refresh Connection button properly.
|
||||
|
||||
## GPC-16609
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the screen displayed GlobalProtect app connection status incorrectly when the device was locked.
|
||||
|
||||
## GPC-16597
|
||||
|
||||
Fixed an issue where the GlobalProtect app stopped working when the app was upgraded from version 5.2.8 to 6.0.3.
|
||||
|
||||
## GPC-16441
|
||||
|
||||
Fixed an issue where the GlobalProtect app connection failed when both GlobalProtect Enforcer and Endpoint Traffic Policy Enforcement were enabled.
|
||||
|
||||
## GPC-16397
|
||||
|
||||
Fixed an issue where the GlobalProtect app was installed on devices running macOS, a blank GlobalProtect app user interface was displayed instead of the correct page.
|
||||
|
||||
## GPC-15697
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, users were able to select All Gateways heading on the page which was not an option for the users to select. This issue happened on the app interface with a non-English language.
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-Linux
|
||||
version: 6.1.4
|
||||
---
|
||||
|
||||
## GPC-19340
|
||||
|
||||
Fixed an issue where the GlobalProtect app failed to send HIP reports hourly.
|
||||
|
||||
## GPC-19331
|
||||
|
||||
Fixed an issue where, when SAML authentication was used to authenticate to the GlobalProtect app, the app used an unknown username SAMLUser which was not configured instead of the actual username of the user, which caused an authentication failure.
|
||||
|
||||
## GPC-19289
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices with Ubuntu 22.04, the app was unable to collect HIP reports.
|
||||
|
||||
## GPC-19280
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app transitions from pre-logon to user-logon tunnel, the app did not display the list of gateways for the users to change the gateway. The gateway list was displayed only when the app was refreshed.
|
||||
|
||||
## GPC-19193
|
||||
|
||||
Fixed an issue where the GlobalProtect app was unable to fetch Windows firewall and antimalware information correctly.
|
||||
|
||||
## GPC-19187
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.0.8 or 6.0.7 was installed on endpoints running macOS Sonoma 14.1, the PanGPS did not work as expected.
|
||||
|
||||
## GPC-19162
|
||||
|
||||
Fixed an issue where, when the user upgraded the GlobalProtect version to 5.2.13 or later version, the HIP report displayed the DLP Digital Guardian Agent as disabled.
|
||||
|
||||
## GPC-19153
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on iOS devices, the users had to reconnect to the GlobalProtect app several times in a day. Users were prompted to enter the credentials every time they tried to reconnect.
|
||||
|
||||
## GPC-19143
|
||||
|
||||
Fixed an issue where the users were unable to choose the correct certificate for the app as the configured registry value previousCertificate did not work as expected.
|
||||
|
||||
## GPC-19104
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP report failed to detect the Real Time Protection status for Cortex XDR, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-19083
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the Connection tab under app Settings did not display the connection status and the refresh connection did not work when the Settings window was opened.
|
||||
|
||||
## GPC-19061
|
||||
|
||||
Fixed an issue where GlobalProtect detected an incorrect Real-Time Protection status for Crowdstrike Falcon during HIP checks for antimalware.
|
||||
|
||||
## GPC-19060
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was installed on devices running macOS, the Connection tab under app Settings did not display the connection status when the app was changed from a non-tunneled gateway to a tunneled gateway.
|
||||
|
||||
## GPC-19044
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the user changed the network from wired to wireless within the organization, the device displayed a blue screen.
|
||||
|
||||
## GPC-19023
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 5.2.13 was installed on devices running macOS, the users were unable to connect to the Zoom application.
|
||||
|
||||
## GPC-19009
|
||||
|
||||
Fixed an issue where, when SAML authentication was used to authenticate to the GlobalProtect app and the user changed the gateway to a manual gateway, the app stayed in the Connecting stage.
|
||||
|
||||
## GPC-18983
|
||||
|
||||
Fixed an issue where the Central Authentication Service (CAS) authentication did not work when the GlobalProtect app was connected to an internal gateway and the app repeatedly opened the SAML authentication page.
|
||||
|
||||
## GPC-18968
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed, You are on the internal corporate network message when users were on a public network. Users had to reboot the system to resolve this issue.
|
||||
|
||||
## GPC-18903
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running on Red Hat version 9, the resolv.conf file was not getting updated with GlobalProtect DNS servers as expected.
|
||||
|
||||
Users should install/uninstall GlobalProtect app using p_install.shand gp_uninstall.shto fix resolve this issue.
|
||||
|
||||
## GPC-18703
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect the Trellix Endpoint Security application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18854
|
||||
|
||||
Fixed an issue where users were prompted twice to authenticate using SAML authentication when used with CAS authentication and authentication override cookie, the GlobalProtect app got stuck in the Connecting stage while trying to connect.
|
||||
|
||||
## GPC-18828
|
||||
|
||||
Fixed an issue where split tunnel CNAME records were created before the GlobalProtect tunnel was established.
|
||||
|
||||
## GPC-18525
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running on Ubuntu 22.04, the app got disconnected intermittently with the error message: Failed to read notify event buffer, error: Resource temporarily unavailable.
|
||||
|
||||
## GPC-16975
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the screen reader did not announce the name of the GlobalProtect gateway when the gateway was marked with the star symbol.
|
||||
|
||||
## GPC-16597
|
||||
|
||||
Fixed an issue where the GlobalProtect app stopped working when the app was upgraded from version 5.2.8 to 6.0.3.
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-Linux
|
||||
version: 6.1.5
|
||||
---
|
||||
|
||||
## GPC-20193
|
||||
|
||||
Fixed an issue where Linux users are disconnected intermittently from GlobalProtect.
|
||||
|
||||
## GPC-20124
|
||||
|
||||
Fixed an issue where GlobalProtect HIP was not working due to a failed OPSWAT library.
|
||||
|
||||
## GPC-19792
|
||||
|
||||
Fixed an issue where an error message was displayed on the GlobalProtect client: "Previous authentication attempt timed out. Please select Connect to initiate authentication once again". Despite this error, the VPN tunnel was established, and traffic was routed successfully through the tunnel.
|
||||
|
||||
## GPC-19748
|
||||
|
||||
Fixed an issue where the GlobalProtect app status was connected but no traffic was passing through. This issue occurred after the GlobalProtect Linux client was upgraded from 6.1.3 to 6.1.4 on Ubuntu Version 22.04.
|
||||
|
||||
## GPC-19353
|
||||
|
||||
Fixed an issue where GlobalProtect was stuck in "Connecting" stage a with "Login Successful!" white page displayed on the default browser instead of the expected Microsoft SAML page.
|
||||
|
||||
## GPC-19297
|
||||
|
||||
Fixed an issue where the Cortex XDR Last full-Scan-Time was not detected on GlobalProtect App for Linux.
|
||||
|
||||
## GPC-18903
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was installed on Linux devices running on Red Hat version 9, the ‘resolv.conf file’ was not getting updated with GlobalProtect DNS servers as expected.
|
||||
|
||||
## GPC-17378
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running System76 coreboot BIOS, the HIP check failed when the Device ID was empty.
|
||||
Reference in New Issue
Block a user