Alejandro Colomar

> Thanks for the PR @doronbehar! > > The file perms are certainly an annoyance, but we'll have to be careful fixing the problem. That `umask(077)` in `main()` goes back...

> > there is a link error, that doesn't appear in CI here. > > Hmm... what errors are you getting? It's always best to start from a completely clean...

> ``` > flatcap | and keep thinking if we need: `set attach_umask = 022` (or $save_umask), `set mailbox_umask = 077` > roccoblues | at least we wouldn't annoy anyone...

> **Update**: Renamed functions -- Prior art in BSD. Thanks, @alejandro-colomar. Ahhh, I didn't find this PR! :-)

Hi @flatcap ! Sorry; I just remembered a detail about recallocarray(3): not only it clears new memory, it also clears the freed memory (like *explicit_bzero*(3)). Maybe we should also clear...

I'll need to test gpg(1) to see what info is available, and what info can be faked. Thanks for the pointers!

I've found this: ```c $ grepc gpgme_decrypt_result_t /usr/include/ /usr/include/gpgme.h:typedef struct _gpgme_op_decrypt_result *gpgme_decrypt_result_t; ``` ```c $ grepc _gpgme_op_decrypt_result /usr/include/ /usr/include/gpgme.h:struct _gpgme_op_decrypt_result { char *unsupported_algorithm; /* Key should not have been used...

I've written some draft to see if it would work, and yeah, looks simple. I'll need to polish it, but it looks simple enough. ```diff commit 79a0f81a378bcf6134ad3019cc68cf01d4d00dfe (HEAD -> gpg)...

@flatcap , do you have any preference for the formatting? Thunderbird shows messages as ``` In addition, this message was encrypted to the owners of the following keys: The message...

This info is available since a7c37625e851ad0585929cf527d89b8dc3e8de60: ``` commit a7c37625e851ad0585929cf527d89b8dc3e8de60 Author: Alejandro Colomar (@alejandro-colomar) Date: Thu Mar 28 23:47:15 2024 +0100 ncrypt/crypt_gpgme.c: Show encryption information Show a block of information about...