Version 7.4.018 bug fixes
-
Fixes an issue where the generation of an authentication payload would fail when using a certificate automatically loaded into the Windows certificate store upon insertion of a smart card or token, but whose private key remains on the smart card or token,
-
Fixes an issue where the Certificate tab would no longer be updated when inserting or removing a token or smart card,
-
When using multiple smart cards, fixes an issue where a tunnel would be closed unexpectedly upon removing a smart card that is not used with the VPN Client,
-
Fixes an issue where VPN Client installation would roll back on Windows 11,
-
In the presence of a redundant gateway, the SPI size in the SA_INIT proposal is set to 8 instead of 0 when the VPN Client switches to the redundant gateway,
-
Fixes an issue where the connection status indicator ring on the TrustedConnect Panel would remain grey during and after TND,
-
Fixes an issue where a tunnel that does not use a token would be closed upon removal of a token,
-
Fixes an issue where a tunnel would not close at the client end when a gateway sends DELETE requests and no longer responds,
-
Fixes an issue where a tunnel would not open when the correct PIN code is entered after initially entering the wrong PIN code,
-
Fixes an issue where the VPN Client would not explicitly ask for the PIN code when a smart card is removed and the reinserted,
-
Fixes an issue where an IKE Reset would be triggered upon inserting a smart card when CPD is enabled,
-
Fixes an issue where path and ngpath keys could be written or deleted,
-
Fixes an issue where a long syslog server name would cause a buffer overflow,
-
Fixes an issue with OpenVPN tunnels where gateway certificate validation was disabled by default,
-
Fixes an issue where a TND beacon port change was not working,
-
Fixes an issue where an “incompatible format” error occurred when retrieving a configuration from an older gateway model,
-
Fixes an issue where the VPN Client would not accept a configuration file from a new gateway model that supports SHA-2 signature algorithms,
-
Fixes an issue where the VPN Client would not accept a self-signed certificate or a certificate used by both the local and remote endpoints,
-
SHA-1 hash algorithm has been reintroduced to support older equipment,
-
Fixes an issue where the Configuration Panel remained accessible from the taskbar icon despite the option restricting access to the Configuration Panel to administrators being enabled,
-
RSASSA-PKCS1-V1_5 signature scheme has been reverted as default to support older equipment.