diff options
Diffstat (limited to 'content/entry/debugging-neomutt.md')
| -rw-r--r-- | content/entry/debugging-neomutt.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/debugging-neomutt.md b/content/entry/debugging-neomutt.md index b4e2f84..ff40926 100644 --- a/content/entry/debugging-neomutt.md +++ b/content/entry/debugging-neomutt.md @@ -8,7 +8,7 @@ About a month ago, I was checking my emails in Neomutt. When I opened a particul I thought maybe this was a one-off. I started Neomutt again and tried to load the same email. It crashed again. Because the crash occurred when trying to open the contents of an email, I was concerned that it may be exploitable. So I started investigating. -I was using the fake system time option in GPG for privacy, which caused problems in other applications. Since the email that crashed my client was encrypted, I suspected the bug had something to do with my esoteric GPG configuration. I found that if I disabled gpgme in Neomutt, the crash went away. +I was using the fake system time option in GPG for privacy, which caused problems in other applications. Since the email that crashed my client was encrypted, I suspected the bug had something to do with my esoteric GPG configuration. I found that if I disabled gpgme in Neomutt, the crash went away. I wasn't sure how to further proceed in debugging, so I joined the Neomutt channel on [Libera Chat](https://libera.chat/), asking for help. I got in touch with [Flatcap](https://github.com/flatcap), the creator of Neomutt. He had me send him the raw email data for the email in question. Since he didn't possess my private key for decrypting it, he could not reproduce the bug. |