gpg: encryption failed: public key not found

Hauke Laging mailinglisten at
Thu Apr 7 20:55:57 CEST 2011

Am Donnerstag 07 April 2011 13:36:31 schrieb 123098:

> If I encrypt the data by command-line I have no problem at all

And "I" is root?

> gpg --encrypt -r "[Recipient's_ID]" [Filename]

This uses the standard keyring nothing else.

> cron is running as root and therefore has access to the key's location

There is a difference between a process being capable of accessing something 
and a process trying to. Do you think root-gpg tries all keyrings it has 
access to automatically?

The easiest way to solve this should be to import the public key as root and 
mark it as "trusted-key" in the config file.

PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20110407/f74030be/attachment.pgp>

More information about the Gnupg-users mailing list