Packet ignored by Linux agent

[RodrigueR]

Good morning,

I believe I followed the Linux agent installation procedure to the letter. I did it from a Debian 10 system. I especially double-checked that the certificate I used in the console to create packages was indeed in the /opt/wapt/ssl directory as required.

However, the Linux agent insists on "ignoring" (discarding) all the packets in my repository:

INFO Discarding mc-winfusionagent-x64(=2.6.0-1) on repo "wapt": None of certificates ("Rodrigue ROYER") are trusted.
...
Total packages: 0
Added packages:

Removed packages:

Discarded packages count: 63

Question: Does this certificate need to have a specific name, because if so, it's not mentioned in the documentation?
Aside from using the -l debug option of the wapt-get update command, what command or log can I look at to understand what's wrong in my case?

WAPT version: 1.8.2.7334 (Community Edition)
Server OS: Debian 10 “Buster”
Operating system of the administration/package creation machine: Windows 10 20h2

[dcardon]

Good evening RodrigueR,
could you please post your control file? There's probably something that doesn't match the Linux agent.
Regards,
Denis

[RodrigueR]

Hello,

I've attached the control file for the Linux package I'm trying to create for Webmin.

This is the first Linux package I've attempted, but I've successfully created others for Windows that are fully functional.

If I'm also getting the same error message for Windows packages, should I assume that this behavior (signature rejection) is normal for packages not intended for the operating system (with the target_os option)?

[dcardon]

The control file is correct (I wanted to check the target_os field, which changed quite a bit between version 1.8 and version 2.0). The certificate file doesn't require a specific format in /opt/wapt/ssl/.
The client discards a package if the package signature doesn't have a matching certificate. Could you please verify that the signing key matches the certificate?
Sincerely,
Denis

[RodrigueR]

Could you please verify that the signing key corresponds to the certificate?

I would be delighted to be able to do this check but I'm afraid I don't really know which commands to run to be able to make this comparison.

In any case, the signer_fingerprint field of this control file corresponds perfectly to the same field in a control file of a Windows package.
However, if you're referring to the signature field, it seems different, but perhaps that's because I shouldn't just read it with a simple text editor, I imagine...