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):
- waptagent.png (6.77 KB) Viewed 2522 times
[RESOLVED] New version 2.3.0.13496 on Debian: Unable to create WAPTagent.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
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?
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?
Last edited by t.heroult on Feb 13, 2023 - 11:11, edited 1 time.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Note: branch 2.2.3 should not be impacted by this bug.
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Yes, updating to version 2.3.0.13503 fixed the problem.
Thank you!
Thank you!
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
