[RESOLVED] [WAPT-Discovery 2.3.0.13516] Package updates no longer possible (setup.py not allowed in manifest)

[fabulousfabs]

Hello everyone,

For about three weeks now, I've been experiencing a strange problem that doesn't seem to be related to any update (or perhaps the update happened relatively seamlessly) )

When I try to update packages on my private repository from the tranquil-it repositories, I encounter the same error message every time:

Errors duplicating package(s):
tis-thunderbird_102.10.0-67_x64_windows_6.1_PROD_fr.wapt: File setup.py is not allowed in manifest of dsin-thunderbird(=102.10.0-67)

This is about Thunderbird, but the error appears regardless of which package I try to update.
I tried reinstalling the console, without effect, and resigning the packages, same result.

I tried some web searches, but "setup.py" returns far too many results unrelated to WAPT, and on this forum "setup.py" doesn't return anything If there are already topics on this subject, I'm sorry, I can't find them -.-'

Thank you to everyone who can help me

Environment :
WAPT Server: Debian 11 stable with WAPT version 2.3.0.13516.
Administration machine - console: Windows Server 2012R2 with console 2.3.0.13516 rev -69968974

Good day

[dcardon]

Hi Fabien,

it's very likely that the certificate being used is a non-code-signing certificate, which can only be used for configuring machines. We need to find the correct certificate, and that should fix it.

That said, the message isn't very clear; we'll see about making it less cryptic...

Best regards,

Denis

[fabulousfabs]

Hello Fabien,

it's very likely that the certificate being used is a non-code-signing certificate, which can only be used to configure machines. We need to find the correct certificate, and that should fix it.

That said, the message isn't very clear; we'll see about making it less cryptic...

Best regards,

Denis

Hello Denis,
Thanks for your reply.

So, I had a doubt about the keys/certificates used, I tried changing them with the other certificates I had on hand, but the result seemed to be the same with all the ones I had on hand (historical), should I try to recreate a private/public key and certificate pair?
Is there a way to find the "name" of the certificate that the console is expecting?

I'm just asking to make the message less cryptic, do you want me to do something specific to get a snippet of the log or a clearer message?

Thank you again
Fabien

[dcardon]

Hi Fabien,

to check if the certificate is code-signing or not, you can double-click the .crt file on a Windows machine, and in the certificate window, on the "Details" tab, you can check if "Code-signing" is selected in the "Advanced Key Usage" attribute.

To find out which certificate has been deployed on your network, you can go to an installed agent and check the directory

Best regards,

Denis

[fabulousfabs]

Hello dcardon, and thank you for your instructions.

Indeed, I didn't have the correct key, neither in C:\program files(x86)\wapt\ssl, nor in C:\program files(x86)\wapt\private, nor even in the old location C:\private.


Luckily, I was able to find the certificate and key I was using in a backup, because for some reason, the files had been deleted from my admin server. Anyway, the problem seems to be solved; the rest has nothing to do with WAPT.

Thanks again, I'm marking this as "solved".

[dcardon]

Thanks for the feedback,
Denis