encryptioncmdpgp

Why does Kleopatra sometimes report a 'No secret key' error, but sometime snot?


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 executed as the same user who have all right.

The application runs every week day in the evening at 6h30pm and sometimes the CMD line returns 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 works fine with other application that run in the morning. And it works fine when I used it.

What can cause this?


Solution

  • 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.