Pulse Secure admins have also discovered that they can resolve the issue by switching to HTML5 Access profiles for their end-users.
For now, it is recommended that users utilize the Pulse Desktop Client instead of connecting via the browser.
ADOBE ACROBAT FREE DOWNLOAD SOFTWARE
Pule Secure says they are working on a fix based on version 9.1R11.x of the client software and hope to have it released by the end of the day. The bug is not affecting users utilizing the Pulse Desktop Client directly, macOS or Linux users, and versions before 9.1R8.x.
ADOBE ACROBAT FREE DOWNLOAD VERIFICATION
"The Code sign verification on the Client-Side components fails because the Certificate expiry time is checked as opposed to the timestamp of the Code signing," a new Pulse Secure bulletin explains. Pulse Secure says that the issue is caused by a bug not correctly verifying that Pule Secure components are signed as it is checking the certificate's expiration date rather than the timestamp on a digitally signed file.Īs the code-signing certificate used to sign the file has expired today, the bug prevents the software from operating correctly, and users are unable to login to VPN devices. In a new support bulletin released today, Pulse Secure explains that "multiple functionalities/features fail for End-Users with a Certificate error." Thus, it allows Windows to consider a file signed even after a certificate becomes invalid. The benefit to timestamps is that it proves that an executable was signed before a certificate expired or revoked. When signing an executable, developers can use an optional time-stamping server that adds an authoritative timestamp to a signature, proving when a file was signed by the certificate.
If a signed executable or DLL is modified somehow, the operating system will no longer consider the program signed and result in warnings or other errors. Bug verifying signed files behind the outageĪ code-signing certificate allows developers to digitally sign program's executables so that Windows and end-users can verify that they have not been tampered with by a third party. This issue affects users globally and is caused by an expired code-signing certificate and a bug in the Pulse Secure software that is not properly verifying that executables are signed. Error when using Pulse Secure client software
0 kommentar(er)
