Hi,

I support an application who call a CMD line to decrypt a file.
The application is a .exe file that is called by the Windows Task Scheduler and is execute as the same user who have all right.

The application run every week day in the evening at 6h30pm and sometimes the CMD line return the message: no secret key.
The application failed because the file was not decrypted. But it doesn't failed every evening, just random evening. It looks totally random.

And if I run the application myself after it failed with the same user, it worked.

The secret key is imported in Kleopatra and it work fine with other application that run in the morning. And it work fine when I used it.

What can cause this?

Thank you

It's not 100% clear to me if you are using Kleopatra via the scheduled task (not sure if that is possible or not) or another tool. It sounds like you tested the secret key in Kleopatra and it worked. If you are using another tool that isn't part of KDE, this forum probably isn't the best place to get an answer. You might try stack exchange and specify exactly what application you are using via task scheduler. Also, you should be checking event viewer logs and any logs the application generates.

Clembo wrote:It's not 100% clear to me if you are using Kleopatra via the scheduled task (not sure if that is possible or not) or another tool. It sounds like you tested the secret key in Kleopatra and it worked. If you are using another tool that isn't part of KDE, this forum probably isn't the best place to get an answer. You might try stack exchange and specify exactly what application you are using via task scheduler. Also, you should be checking event viewer logs and any logs the application generates.

The task scheduler just call a C# .exe that download a file and decrypt it with a command line like :
gpg2 --output "my new file" --batch --passphrase "my passphrase" --default-key "my key" --decrypt "my file"

The problem is with the key.

But we tested a new thing, when the user (user specified in the task scheduler ) is sign out, one key in particular fail to decrypt. There is similar .exe applications that use other key and they don't fail.

We fix the problem. We must not log off the application user.
If we log off the user, one key is not working, but the others are working.