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 ff40926..714aced 100644 --- a/content/entry/debugging-neomutt.md +++ b/content/entry/debugging-neomutt.md @@ -14,7 +14,7 @@ I wasn't sure how to further proceed in debugging, so I joined the Neomutt chann I wasn't about to send him my private key. Someone else suggested I could decrypt the email with my private key, then reencrypt it with a new private key I wouldn't mind divulging. Luckily I knew of a better way. GPG has the "--show-session-key" option. It's used to allow others to decrypt specific messages intended for you without giving them your private key. -The Neomutt developers edited their GPG options inside the Neomutt configuration so it would successfully decrypt the original email. They used "--override-session-key <string>". Their clients did not crash when opening the email. At that point, I knew the cause was my GPG configuration. Still, an esoteric configuration should not cause Neomutt to core dump. Core dumps should never happen. So I was determined to find the root cause of the bug. +The Neomutt developers edited their GPG options inside the Neomutt configuration so it would successfully decrypt the original email. They used "--override-session-key [string]". Their clients did not crash when opening the email. At that point, I knew the cause was my GPG configuration. Still, an esoteric configuration should not cause Neomutt to core dump. Core dumps should never happen. So I was determined to find the root cause of the bug. Since Flatcap couldn't reproduce the crash, the only option left was to debug it myself. Flatcap helped me to compile Neomutt from source so I'd have the debugging symbols. Then he explained how to attach GDB to the Neomutt process. I proceeded to purposely crash Neomutt. |