Alejandro Colomar

> > A quick look at the crash (it's late here)... I see: > > ``` > > (gdb) p *state > > $2 = {fp_in = 0x615000016600, fp_out =...

v3 changes: - Fix crash (make the print conditional) - Explicitly test `!= NULL` (@flatcap , is that OK? I see mixed style in the project) - Add feature page...

v3b changes: - Fix indentation. - Explicitly test `!= NULL` in loop controlling expression ``` $ git range-diff main gh/gpg gpg 1: cb4c830dc ! 1: a3274d3bf ncrypt/crypt_gpgme.c: Show encryption information...

When does the *pgp_gpgme_application_handler*() handler run? I don't know how to test it. :|

> application/pgp Would you mind sending me an email with such an attachment? I don't know how to write one. ;)

> > application/pgp > > Would you mind sending me an email with such an attachment? I don't know how to write one. ;) Ahh, this worked: attaching an encrypted...

I'm done with testing, I think. There are a couple of things that I have doubts: - Is it possible to fake a recipient? This wouldn't be our problem, as...

v4 changes: - Also show the encryption information block in the application/pgp handler when there are decryption errors. ``` $ git range-diff main gh/gpg gpg 1: a3274d3bf ! 1: ba8b0219f...

v4b changes: - Reduce scope of variable ``` $ git range-diff main gh/gpg gpg 1: ba8b0219f ! 1: 0a875fb63 ncrypt/crypt_gpgme.c: Show encryption information @@ ncrypt/crypt_gpgme.c: restart: { maybe_signed = true;...

v4c changes: - Rebase on main. - Document @flatcap 's help during development of the patch. - Clarify the relation with bug #4223 in the commit message. - Hide current...