Solution: Crontab running gpg script can’t find secret key

[Ingo Klöcker]

On Thursday 03 February 2011, griffmcc wrote:
> Here's what works for me:
> 
> 
> echo 'password' | gpg -vvv --homedir /root/.gnupg --batch
> --passphrase-fd 0 --output /usr/share/file.gpg --encrypt --sign
> /usr/share/file.tar.bz2

I suggest setting the passphrase of the key to an empty passphrase. 
Using a non-empty passphrase and then putting this "secret" passphrase 
in the crontab totally defeats the purpose of the passphrase. Moreover, 
the passphrase will be available to anybody who knows ps.


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20110203/c7a86ca6/attachment-0001.pgp>