Comment by ~ctrm on ~sircmpwn/aerc2
Can the rationale be elaborated a bit more? I know I can't come here with demands for features, at least unless I'm ready to submit patches, but an explanation a bit better than "has been discussed on irc and it's a no" would at least prevent duplicate tickets.
RESOLVED WONT_FIX REPORTED
Comment by ~ctrm on ~sircmpwn/aerc2
Well, this is similar to https://todo.sr.ht/~sircmpwn/aerc2/420, which has been closed as a WONTFIX for no clear reason.
Ticket created by ~ctrm on ~sircmpwn/aerc2
Hi,
I understand that aerc implements its own keyring pgp, and this may be easier for users using pgp solely within their email client. This is however often not the case, for example I use GPG for
- password storage (via pass)
- SSH pubkey authentication
- manual signing of files to be released
- manual verification of signatures
- I keep my keys in a smartcard
As you see GnuPG won't go away, and maintaining a single keyring is already painful enough, really.
Could aerc implement a gpg-agent client to optionally give access to the GnuPG keyring? From a quick search looks like there are Go libraries allowing it.
In any case thanks for aerc, it's some fresh air after years if not decades of frustration with the existing email clients.