[RESOLVED] Package resignation failed

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

October 5, 2022 - 11:48

Hello,

- WAPT Enterprise 2.2.3.12463
- agent version: 2.2.1
- server OS (Linux)
- administration OS (Windows)

I'm having trouble re-signing a package that was created (internally) with a key that is no longer on the server (the agent who developed them had to recreate their key after losing their password, so the packages they developed use this old key). How can I do this? Should we delete these packages and then recreate them?

Thank you in advance, Best regards.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

October 6, 2022 - 10:15

Hello,

the console refuses to modify a package whose origin (i.e., signature) it cannot validate.

To fix the problem, you can download the package locally from the private repository and re-sign it by re-uploading it.

Regards,

Denis
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
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

October 6, 2022 - 11:01

Hello,

that's what I tried to do but even "Edit a package in the editor" is blocked (see attached).

Thank you.
Attachments
Screenshot from 2022-10-06 10:56:40.png
Screenshot from 2022-10-06 10:56:40.png (15.94 KB) Viewed 4519 times
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

October 11, 2022 - 9:30 AM

Another way is to copy the URL from the private repository into the console and download it using a browser.

The console tries to protect the admin from a malicious package by first verifying that the signature is known. We should be able to temporarily disable this protection in your case. We'll look into what we can do internally.

Regards,

Denis
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
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

October 11, 2022 - 3:20 PM

Hello,

it's all good, I did indeed "Download packages" for the package in question from the console, extracted the .wapt file, and then opened it with PyScripter. The resigning was successful.

Thank you!
Locked