Package: gnupg
Version: 1.4.1-1
Hello,
When using gpg for symmetric encryption/decryption, the key is deduced
from a passphrase; it has no need to access pubring and secring. If,
in addition, the options "--no-options --no-random-seed-file" are used,
there is no need at all to access $HOME/.gnupg. Yet gpg does.
For encryption, one can add "--no-default-keyring --keyring /dev/null"
but this is a workaround. (It relates to bug 200183.)
For decryption, I have not found any way to prevent gpg from trying to
access the secring. With "--lock-never --homedir /nowhere", it will
neither read nor create anything sensitive, but it will report errors.
This may be related to bug 67564, except that the justification given
(that secring is needed to know how trusted the key is) does not apply.
This is a problem for automated system administration scripts which
need to use gpg for encryption, depending on whether the user they run
as has a home directory. One can work around it by creating temporary
directories each time gpg is run, but IMNSHO it would be better if it
did not attempt to access files unnecessarily in the first place...
Thank you,
Cedric Ware.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
