Tranquil IT Forum

Good morning

I just installed the new version, updated my console with waptsetup, as usual, but when creating the new agent (after validating the agent configuration window): Any ideas?

Hi Thomas,

the code signing certificate used in the build expired early this morning. This shouldn't have been a problem because the signatures are timestamped, and the checks are performed against the time the file was signed and timestamped. However, during agent creation, when verifying the agent's signature against the manifest, the code only checks the certificate's validity date, whereas it should verify that the timestamp is within the certificate's validity range. So, there's an overly strict bug in the WAPT code...

A new build was prepared over the weekend and is currently being validated. If it's urgent, you can use the release that was just pushed. There's a bug related to the CRL machine validation (a non-standard configuration that you shouldn't have unless you explicitly configured it manually in the configuration files), otherwise, there shouldn't be any problems.

The changelog has just been pushed online [1].

Sorry for the inconvenience.

For better topic indexing, I'm adding the message here in text format: "Error creating waptagent.exe: Tranquil IT signature verification of the control hashes on the server failed. Check that waptbinaries.sha256 has not been altered on the server."

Regards,

Denis

[1] https://www.wapt.fr/en/doc/wapt-changel ... 2023-02-13

Note: branch 2.2.3 should not be impacted by this bug.

Yes, updating to version 2.3.0.13503 fixed the problem.

Thank you!