I do this but don't use the module, just the shell.
You have to confirm the environment for the user. I reset HOME.
$ENV{'HOME'}=/home/gnupg;
.gnupg directory permission has to be 0700 owned by the webserver user, with
0600 on the files.
Plaintext is encrypted to the key and then securely
Check error_log for the problem (if you can) - permissions on ~/.gnupg files
will cause things to not work and you must have environment exported for the
nobody user. I reset $ENV{'HOME'} in perl... there must be something
similar in php. If you can view the environment the server provides in
get over it, publishing your email results in spam; I don't think that this
suprises anyone anymore - deal with it in your own way and move on. The rage
against spam has resulted in excellent filtering software, but the
energy on both sides amounts to equilibrium.
Stef
$OK | mail -s `hostname` backup $OK you
Stef Caunter
http://caunter.ca/contact.html
Is there any documentation on how to do that?
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
I'm sure I have just missed this in the archives, but I cannot see mention of a
way to get sufficient randomness when running gpg remotely in a shell account
to batch generate key pairs, i.e.
gpg --gen-key --batch tmp
where tmp is populated according to doc/DETAILS example. Here is what I've
