[RESOLVED] Strange error during update to 2.5.3

[guigeek]

Hi!
After updating to version 2.5.3 on Debian 12, I'm getting the following error when creating the agent:

"Error white creating waptagent.exe: Checking hashes of executables on server against TranquitIT certificate has failed.
Please check if waptbinaries.sha256 has not been altered."

I saw that this bug was present in version 2.3 but seemed to be fixed afterward.

Any idea what the procedure is in this case?

Thanks!

[dcardon]

Hello Guillaume,

There is a bug in the signature verification of waptsetup.exe from the console... Our old code signing key for signing executables expired this weekend, which is not a problem in itself because normally the signing mechanism validates that the certificate was valid at the time of signing.

The bug is that the console correctly verifies the certificate, but should only accept it if the signing occurred within the certificate's validity period (which is indeed the case). However, in this particular bug, the validation is based on the current date for the waptbinaries.sha256 file...

We are currently fixing this. In the meantime, you can launch the agent creation process via the command line; the signature verification of the waptbinaries.sha256 file is only performed in the console.

Code: Select all

"C:\Program Files (x86)\wapt\wapt-get.exe" build-waptagent -c "%localappdata%\waptconsole\waptconsole.ini"

Alternatively, wait until tomorrow before doing the upgrade to give us time to push the update.

Sincerely,

Denis

[guigeek]

Thanks so much!

[Marceld]

Good morning,

We're experiencing the same problem after upgrading from version 2.4.0.14143

And what identifier should we enter here?

wapt.PNG (7.48 KB) Viewed 11293 times

We tried using the console access credentials but it doesn't work (same for a VM (admin) user)

[guigeek]

Good morning,
I just installed the latest update, so I'm now on version 2.5.4.
But when creating the agent, I now get the following error:
"Error white creating waptagent.exe: waptsetupe.exe is not digitally signed or not signed by Tranquit IT. Aborting"

Any ideas?

Hello Guillaume,

There is a bug in the signature verification of waptsetup.exe from the console... Our old code signing key for signing executables expired this weekend, which is not a problem in itself because normally the signing mechanism validates that the certificate was valid at the time of signing.

The bug is that the console correctly verifies the certificate, but should only accept it if the signing occurred within the certificate's validity period (which is indeed the case). However, in this particular bug, the validation is based on the current date for the waptbinaries.sha256 file...

We are currently fixing this. In the meantime, you can launch the agent creation process via the command line; the signature verification of the waptbinaries.sha256 file is only performed in the console.

Code: Select all

"C:\Program Files (x86)\wapt\wapt-get.exe" build-waptagent -c "%localappdata%\waptconsole\waptconsole.ini"

Alternatively, wait until tomorrow before doing the upgrade to give us time to push the update.

Sincerely,

Denis

[sfonteneau]

Hello,

is this indeed version 2.5.4.15335?

The changelog and upgrade procedure are currently being written.

You need to manually install waptsetup 2.5.4.15335 and make sure to change waptdeploy in your GPOs.

- Simon

[guigeek]

Yes, that's the one
. I installed WaptSetup manually. But I don't have a GPO because I don't have Active Directory.

[sfonteneau]

And the server has also been upgraded to 2.5.4.15335?

You can check on the WAPT server's web interface.

[guigeek]

[Marceld]

Good morning,

We have exactly the same problem; we do have the latest local package (2.5.4.15335):

wapterreurX.PNG (4.18 KB) Viewed 11026 times

THANKS