Remove dates from issue filenames
This commit is contained in:
@@ -0,0 +1,79 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-Linux
|
||||
version: 6.2.6
|
||||
---
|
||||
|
||||
## GPC-22950
|
||||
|
||||
Fixed an intermittent issue on Linux machines that affected users' ability to perform Web searches on browsers while connected to the GlobalProtect app.
|
||||
|
||||
## GPC-22872
|
||||
|
||||
Fixed an issue while installing the GlobalProtect app version 6.2.1.1-7 on Fedora 41 x86_64 Linux machines by executing gp_install.sh script on command line interface did not work as expected.
|
||||
|
||||
## GPC-22774
|
||||
|
||||
Fixed an issue where GlobalProtect app 6.2.1-7 was installed on Linux Fedora machines, the import certificate failed due to missing /etc/ssl/private/ directory.
|
||||
|
||||
## GPC-22766
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux machines, hyperlink in the welcome page opened in the embedded browser instead of default browser.
|
||||
|
||||
## GPC-22390
|
||||
|
||||
Fixed an issue where the GlobalProtect app version 6.2.1 did not fetch the portal address from pre-deployed pangps.xml.
|
||||
|
||||
## GPC-22306
|
||||
|
||||
Fixed an issue where the GlobalProtect app tray icon failed to display when the app was installed on devices running Linux Ubuntu 24.04.1 LTS.
|
||||
|
||||
## GPC-22249
|
||||
|
||||
Fixed an issue where some of the third party license files were missing in the GlobalProtect app packages.
|
||||
|
||||
## GPC-22130
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed the following incorrect error message when there was no internet connectivity:
|
||||
|
||||
**Could not verify the server of the gateway. If the issue persists, contact your administrator.**
|
||||
|
||||
## GPC-22051
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed the following unexpected client certificate error message during portal logon: **Valid client certificate required for authentication**, when **Allow Authentication with User Credentials OR Client Certificate** option was set to **Yes**.
|
||||
|
||||
## GPC-21951
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux machines, the virtual adapter maintained tunnel IP even when the app was disconnected.
|
||||
|
||||
## GPC-21920
|
||||
|
||||
Fixed an issue where the GlobalProtect app web interface did not display some settings such as portal address when the user manually disconnected the app and then restarted.
|
||||
|
||||
## GPC-21915
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux Ubuntu LTE 20.04 machines, the GlobalProtect app did not properly display the connection status and the app was incorrectly positioned in the middle of the screen.
|
||||
|
||||
## GPC-21861
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices (Ubuntu 22.04.4 LTS), the tunnel got disconnected intermittently causing connectivity issues.
|
||||
|
||||
## GPC-21762
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app is installed on Linux RHEL 8.9, PanGPA process stopped and failed to recover automatically impacting the functioning of the GlobalProtect app.
|
||||
|
||||
## GPC-21724
|
||||
|
||||
Fixed an issue where the IoT GlobalProtect app connection failed after system reboot with error: **cannot connect to local gpd service**.
|
||||
|
||||
## GPC-21651
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app is installed on Linux RHEL 8.9,the app did not remove the configured DNS even after disabling the app.
|
||||
|
||||
## GPC-21092
|
||||
|
||||
Fixed an issue on Linux machines where users were unable to authenticate to the GlobalProtect app using certificate authentication. Despite the certificate being sent to the firewall, the app was defaulting to SAML authentication method.
|
||||
|
||||
## GPC-21478
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.2.0-265 was installed on Linux machines running Ubuntu 24.04.1 LTS, the app got stuck and users were unable to connect to the app after system reboot.
|
||||
Reference in New Issue
Block a user