Josef Wolf wrote:
> Hello!
>
> I need a setup where the user running "gpg -e -r foobar" is not able to
> modify keyring contents. I tried:
>
> # chown -R root:user ~user/.gnupg
> # chmod -R o=rwX,g=rX,o= ~user/.gnupg
>
> Unfortunately, this don't work because gpg does some write operati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings GnuPG and Pine users,
I'm announcing a newly developed pine and gpg wrapper utility, which
accommodates encryption, clear-signing, decryption and verification,
specifically integrated with pine to handle multiple roles. I am
releasing pi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Josef Wolf wrote:
> 1. It locks the keyring. --lock-never will avoid this. Is it safe
> to use --lock-never as long as it is guaranteed that _only_ "gpg -e"
> is ever run? No key generation, no imports, no signung. Only
> "gpg -e".
Hello!
I need a setup where the user running "gpg -e -r foobar" is not able to
modify keyring contents. I tried:
# chown -R root:user ~user/.gnupg
# chmod -R o=rwX,g=rX,o= ~user/.gnupg
Unfortunately, this don't work because gpg does some write operations
in its .gnupg directory:
1. It
Hello!
I need a setup where the user running "gpg -e -r foobar" is not able to
modify keyring contents. I tried:
# chown -R root:user ~user/.gnupg
# chmod -R o=rwX,g=rX,o= ~user/.gnupg
Unfortunately, this don't work because gpg does some write operations
in its .gnupg directory:
1. It
