On Sun, Apr 02, 2017 at 01:06:29AM +0200, gregor herrmann wrote:
On Sat, 01 Apr 2017 15:40:17 -0700, Sean Whitton wrote:
Currently, I have mutt pass `--keyring /usr/share/keyrings/...` for each
of the keyrings, so that I can verify signatures on e-mails. It would
be more natural to just add `keyring /usr/share/keyrings/...` to
~/.gnupg/gpg.conf, but when I tried this I often got errors from gpg
trying to write to the keyrings in /usr/share/keyrings. Is there some
way to mark a keyring as read-only?
I'm using the keyrings from keyring.debian.org instead of the
packaged ones. That way they are up to date and I don't have the
write errors:
% crontab -l | grep debian-keyring
30 17 * * * /usr/bin/rsync -rlptDq
"keyring.debian.org::keyrings/keyrings/*.gpg" /home/gregoa/.gnupg/debian-keyring
(copied from someone/somewhere)
% grep debian-keyring ~/.gnupg/gpg.conf
keyring /home/gregoa/.gnupg/debian-keyring/debian-keyring.gpg
keyring /home/gregoa/.gnupg/debian-keyring/debian-maintainers.gpg
keyring /home/gregoa/.gnupg/debian-keyring/debian-nonupload.gpg
keyring /home/gregoa/.gnupg/debian-keyring/debian-role-keys.gpg
keyring /home/gregoa/.gnupg/debian-keyring/emeritus-keyring.gpg
I can see you are using mutt as well, when you try sign an email,
doesn't mutt complain?
"ambiguous specification of secret key $KEYID" it's what I got then I
cannot sign any email
thanks!
--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
keybase: https://keybase.io/gfa
