New answers tagged gpg
It looks like Dale Woolridge's confirm-crypt-hook patch has been merged into mutt. use crypt-hook rather than pgp-hook. crypt-hook email@example.com 0x123456789ABCDE01 set crypt_confirmhook=no for that recipient. e.g. send-hook ~t firstname.lastname@example.org 'set crypt_confirmhook=no' This should work with mutt or neomutt.
I don't know if you can that, it's kind of violating the point of setting an expiry date. But you can probably trick gpg by running it in some kind of virtual machine that allows you to set the time to shortly before the old key expired. I don't know if gpg will let you sign a key that's not yet valid, but then you'll just have to make a new new key in that ...
Good answer but here's a couple of clarifications: "Gpg-agent can't do this yet, it is a planned feature. SSH has had agent forwarding for a very long time. (This is a reason not to use gpg-agent for SSH keys.)" Not quite true. gpg-agent works fine with SSH agent forwarding. I use it every day. The SSH client handles the forwarding, gpg-agent is not ...
progress can do this for you — not quite a progress bar, but it will show progress (as a percentage) and the current file being processed (when multiple files are processed): gpg ... & progress -mp $!
To get the cacheid you need to mention --fingerprint twice, for example: $ gpg --fingerprint --fingerprint email@example.com pub 1024D/517D0F0E 2000-10-10 Key fingerprint = C75D C40A 11D7 AF88 9981 ED5B C86B A06A 517D 0F0E uid Linux Kernel Archives Verification Key <firstname.lastname@example.org> sub 4096g/E50A8F2A 2000-10-10 ...
Top 50 recent answers are included