Page 1 of 1

[RESOLVED] Package resignation failed

Published: October 5, 2022 - 11:48 AM
by thomas789
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.

Re: Unable to resign packages

Published: October 6, 2022 - 10:15 AM
by dcardon
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

Re: Unable to resign packages

Published: October 6, 2022 - 11:01 AM
by thomas789
Hello,

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

Thank you.

Re: Unable to resign packages

Published: October 11, 2022 - 9:30 AM
by dcardon
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

[SOLVED] Re: Resigning packets impossible

Published: October 11, 2022 - 3:20 PM
by thomas789
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!