~rjarry added pgp 1 year, 3 months ago

~rjarry added ui 1 year, 3 months ago

~rjarry added feature 1 year, 3 months ago

~mcepl 1 year, 3 months ago*

Isn’t that a problem of any TUI application? How is it supposed to work? How does it work with mutt (for example)? Wouldn’t pinentry-curses (or the appropriate pinentry for your GUI environment) work better?

~emmatebibyte 1 year, 3 months ago

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.

~rjarry added bug 1 year, 2 months ago

~rjarry removed feature 1 year, 2 months ago

~stacyharper referenced this from #270 8 months ago

~kyllingstad 7 months ago

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:

1. I compose a new email.
2. At the "Send this email?" prompt, I press y.
3. 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.
4. 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.

~rjarry REPORTED FIXED 6 months ago

Koni Marti referenced this ticket in commit 163ea3e.