Tranquil IT Forum

Hi,

In order to manage the uninstallation of software not deployed by WAPT, I'm trying to create an empty package to accomplish this task.

The problem is that using the `build-upload` command (and the `build package` command as well) returns an error after prompting for the private key password.
The password is correct, but it contains special characters: hyphens and accented characters.

I've tried using the command prompt, PowerShell, and logging in as a local administrator on the machine... nothing works.

The error message is: FATAL ERROR: EWaptMissingPrivateKey: The key matching the certificate C:\private\xxx.crt cannot be found or decrypted.


I've tested via the console, using an .msi file, and the package is correctly signed and lands successfully in my repository.

Do you know if the problem could stem from the use of special characters?
Do you have a workaround?
Thanks

Hello Sones,

sones wrote: ↑May 2, 2019 - 12:37 PM To manage the uninstallation of software not deployed by WAPT, I'm trying to create an empty package to accomplish this task.

The problem is that using the build-upload command (and the build package command too...) returns an error after prompting for the private key password.
The password is correct, but it contains special characters: hyphens and accented characters.

I've tested it in cmd, in PowerShell, by logging in as a local administrator on the machine... nothing works.

The error message is: FATAL ERROR: EWaptMissingPrivateKey: The key matching the certificate C:\private\xxx.crt cannot be found or decrypted.


I tested via the console, using an .msi file; the package is correctly signed and lands successfully in my repository.

Do you know if the problem could stem from the use of special characters?
Do you have a workaround?

There might be a Unicode problem somewhere. What version of WAPT, OS, etc. (cf. viewtopic.php?f=9&t=886) ?
You can try changing the signature key password through the console (if there are no unicode problems, menu "tools/ change private key password").

Sincerely,

Denis

Thanks for the feedback:

- WAPT version installed (1.7)
- Server OS (Linux Debian Stretch)
- Administration/package creation machine OS (Windows Server 2016)

I haven't had time to test the key change yet; I recently went from 50 machines in the inventory to over 400.

Does changing the key also mean re-signing all packages/distributing the .pem file to client machines?

Denis was talking about changing the "password" of the key, not the key itself. The key itself doesn't change, only its encrypted representation in the .pem file.
So there's no impact on the packet signature.

OK, changing the password solved my problem.

Thank you both.