Hey guys, just a head's up to mention that I've added initial support for PGP to aerc. Right now, it supports signature verification and message decryption. If you'd like to give it a try, batteries are not yet included. aerc manages its own keyring, separately from GPG. If you want to bootstrap it from GPG, run the following commands: gpg --export >> ~/.local/share/aerc/keyring.asc gpg --export-secret-keys >> ~/.local/share/aerc/keyring.asc This will be made easier later. I've filed the follow-up work in the following tickets: https://todo.sr.ht/~sircmpwn/aerc2?search=label:%22pgp%22 Feedback welcome.
Just curious, why did you decide to keep your own keyring? I'm fairly unlikely to put my key anywhere that's not my hardware token.
I already said why: to reduce the footguns. I want PGP support to be plug and play, and to do the right thing with zero configuration. It should just werk. We can add support for hardware tokens later.
Wouldn't it be better then to use GPG if available and fall back to the internal tooling if it is not? Or at least making the use of shell GPG optional. I think I am not the only one uncomfortable with just straight up exporting my secret keys. > It should just werk. This is a great tenet for working, but I think having the freedom to configure this would allow for a more fine-grained control for advanced users. Like, using the mutt defaults  which are pretty decent IMHO. :https://gitlab.com/muttmua/mutt/-/blob/master/contrib/gpg.rc