On Mon 14 Nov 2022 at 11:39:11 (-0500), Greg Wooledge wrote:
> On Mon, Nov 14, 2022 at 07:33:00PM +0300, Gökşin Akdeniz wrote:
> > 14.11.2022 15:26 tarihinde Anssi Saari yazdı:
> > >
> > > So does mutt try to check the PGP signature in Gökşin's message and
> > > crash due to that or some other issue?
> > >
> >
> > I use Thunderbird for reading, composing,sending e-mail and signing and
> > encrypting, decrypting e-mail messages.
> >
> > Probably it is why mutt and GnuPG had troubles.
>
> This message also caused mutt to segfault when I tried to open it and
> read it. I can press L from the index to reply-to-list, which I'm
> doing now. But I can't read the original.
>
> If anyone figures out a way to make mutt NOT segfault when reading this
> type of email, I'd love to hear it.
No problem here on bullseye with mutt "Mutt/2.0.5 (2021-01-21)", but
that might be because I'm unconcerned about checking signatures, so
something might be uninstalled or unconfigured. Here's what I see
when Gökşin Akdeniz's second message is read:
--✄--------
Date: Mon, 14 Nov 2022 19:33:00 +0300
From: Gökşin Akdeniz <goksin.akde...@gmail.com>
Subject: Re: Causing segmentations fault; Was: Re: No Public Key
X-Original-To: deb...@lionunicorn.co.uk
X-Original-To: lists-debian-u...@bendel.debian.org
[-- PGP output follows (current time: Mon Nov 14 11:05:42 2022) --]
gpg: keyblock resource '/usr/share/keyrings/debian-keyring.pgp': No such file
or directory
gpg: Signature made Mon Nov 14 10:33:00 2022 CST
gpg: using EDDSA key 9BD18DF7E46ECBFB0E468C6D648AAD2AAA3BAD5F
gpg: Can't check signature: No public key
[-- End of PGP output --]
[-- The following data is signed --]
Subject: Re: Causing segmentations fault; Was: Re: No Public Key
[-- Attachment #1 --]
[-- Type: multipart/mixed, Encoding: 7bit, Size: 9.0K --]
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: base64, Size: 0.5K --]
14.11.2022 15:26 tarihinde Anssi Saari yazdı:
>
> So does mutt try to check the PGP signature in Gökşin's message and
> crash due to that or some other issue?
>
I use Thunderbird for reading, composing,sending e-mail and signing and
encrypting, decrypting e-mail messages.
Probably it is why mutt and GnuPG had troubles.
[-- Attachment #2: OpenPGP public key --]
[-- Type: application/pgp-keys, Encoding: quoted-printable, Size: 8.1K --]
[-- PGP output follows (current time: Mon Nov 14 11:05:42 2022) --]
gpg: keyblock resource '/usr/share/keyrings/debian-keyring.pgp': No such file
or directory
[-- End of PGP output --]
[-- BEGIN PGP PUBLIC KEY BLOCK --]
pub ed25519 2022-02-13 [SC] [expires: 2023-02-13]
9BD18DF7E46ECBFB0E468C6D648AAD2AAA3BAD5F
uid Gökşin Akdeniz (*BSD User, GNU/Linux User, eniXma Founder, eniXma
Author, Scholar)
+<goksin.akde...@gmail.com>
sub cv25519 2022-02-13 [E] [expires: 2023-02-13]
pub rsa4096 2020-02-08 [SCEA] [revoked: 2021-03-29]
D33E279317FA00ACB438E040F4E1EEA55B6F910A
sub rsa4096 2020-02-08 [E] [revoked: 2021-03-29]
pub rsa2048 2015-01-06 [SCEA] [revoked: 2016-05-04]
5584E544E1541B128ADD4802DDC4D6DAAC7DCCF7
sub rsa2048 2015-01-06 [E] [revoked: 2016-05-04]
pub rsa4096 2019-02-06 [SCEA] [revoked: 2020-02-08]
00E7125AF1F0BD88BAB4D5E9443D65289EFEC656
sub rsa4096 2019-02-06 [E] [revoked: 2020-02-08]
[-- END PGP PUBLIC KEY BLOCK --]
[-- End of signed data --]
--✄--------
Make of that what you will.
Cheers,
David.
