Josef Wolf wrote:
>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
You'd better use chattr -i on it.
>to use --lock-never as long as it is guarantee
Thanks for the suggestion. Your "pipeline assumption" was correct.
I have an Exabyte SCSI-3 tape drive which is faster than most DAT
drives, so it is worth it to see if I can get "encrypted backups" to
work easily enough. Next - I will be experimenting with encrypting
backups via ISO (CD images),
Hi,
We are pleased to announce version 1.4 of libgpg-error,
a library for common error values and messages in GnuPG components.
This is a shared library so it can be updated independently of each
individual component, while still allowing the use of new error values in
inter-process communication
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Was Fri, 08 Sep 2006, at 08:23:35 +0200,
when Werner wrote:
> On Thu, 7 Sep 2006 22:57, Mica Mijatovic said:
>> And when I'm already at the desk, just a brief note that if a source
>> code is being delivered as well, to the users, then it
