When I try to encrypt an e-mail to someone with my PGP key, the pinentry-tty prompt tries to request my key’s password, which breaks the UI.
Isn’t that a problem of any TUI application? How is it supposed to work? How does it work with
mutt
(for example)? Wouldn’tpinentry-curses
(or the appropriatepinentry
for your GUI environment) work better?
After deliberation in the IRC, I was told this could possibly be solved. I would rather not use pinentry-curses because my main use of my pgp key is signing git commits and a simple prompt is less disruptive. I refuse to use a graphical pinentry program.
I’m not sure how it works with mutt, I’ve always found it uncomfortable to use so I avoided it.
Neither pinentry-tty nor pinentry-curses work for me, only the GUI variants (when run under a graphical environment). In addition, when the signing fails because of this, aerc sends an empty mail to the recipient.
Specifically, what happens is this:
- I compose a new email.
- At the "Send this email?" prompt, I press
y
.- The message “failed to parse messagedetails: FAILURE sign <hex code>“ appears in the status bar, and nothing else appears to happen – I'm still at the send prompt.
- In reality, a message has been sent to the recipient with an empty subject, empty body, and no signature.
I am using aerc 0.18.2 on Debian 12.
Koni Marti referenced this ticket in commit 163ea3e.