Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Greg Wooledge
On Mon, Nov 14, 2022 at 08:44:54PM -, Curt wrote: > On 2022-11-14, wrote: > > > >> https://gitlab.com/muttmua/mutt/-/issues/428 > > > > Is there a non-javascript-ey way to look at those issues? > > > > > Mutt crashes with SIGSEGV when uid -variable is NULL in > pgp_gpgme_extrace_keys(). >

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Curt
On 2022-11-14, wrote: > >> https://gitlab.com/muttmua/mutt/-/issues/428 > > Is there a non-javascript-ey way to look at those issues? > Mutt crashes with SIGSEGV when uid -variable is NULL in pgp_gpgme_extrace_keys(). Found in Mutt 2.0.5 (Debian 11 + 2.0.5-4.1+deb11u1). Reproducible in: 2.1

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread tomas
On Mon, Nov 14, 2022 at 05:46:25PM +0100, Sven Joachim wrote: > On 2022-11-14 11:39 -0500, Greg Wooledge wrote: > > > If anyone figures out a way to make mutt NOT segfault when reading this > > type of email, I'd love to hear it. > > Upgrading to 2.2.8 or later should do the trick. I can confirm

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread David Wright
7;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: --✄---

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Sven Joachim
On 2022-11-14 11:39 -0500, Greg Wooledge wrote: > If anyone figures out a way to make mutt NOT segfault when reading this > type of email, I'd love to hear it. Upgrading to 2.2.8 or later should do the trick. I can confirm that mutt 2.2.9-1 in unstable no longer segfaults displaying the message

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Greg Wooledge
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

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Gökşin Akdeniz
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 mut

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Anssi Saari
steve writes: > Le 14-11-2022, à 08:58:02 +0100, to...@tuxteam.de a écrit : > >>On Mon, Nov 14, 2022 at 08:51:47AM +0100, Henning Follmann wrote: >> >>[...] >> >>> Mutt crashes trying to open this post (while opening gnupg). >>> That's weird. >> >>Confirmed. > > Here too. > > mutt 2.2.7 (2022-08-

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread Thomas Pircher
Henning Follmann wrote: Mutt crashes trying to open this post (while opening gnupg). That's weird. When I save the message as attachment, and run gnupg over it, I get this error message | gpg: CRC error; 3B73F1 - DC33B7 | gpg: quoted printable character in armor - probably a buggy MTA has been

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-14 Thread steve
Le 14-11-2022, à 08:58:02 +0100, to...@tuxteam.de a écrit : On Mon, Nov 14, 2022 at 08:51:47AM +0100, Henning Follmann wrote: [...] Mutt crashes trying to open this post (while opening gnupg). That's weird. Confirmed. Here too. mutt 2.2.7 (2022-08-07)

Re: No Public Key

2022-11-14 Thread Thomas Schmitt
Hi, Thomas George wrote: > I thought to skip this step and tried > gpg --verify SHA515SUMS.sign.txt debian-11.5.0-amd64-netinst.iso That's not the right way. SHA515SUMS.sign verifies SHA515SUMS SHA515SUMS verifies debian-11.5.0-amd64-netinst.iso The latter step can be done by this command in the

Re: Causing segmentations fault; Was: Re: No Public Key

2022-11-13 Thread tomas
On Mon, Nov 14, 2022 at 08:51:47AM +0100, Henning Follmann wrote: [...] > Mutt crashes trying to open this post (while opening gnupg). > That's weird. Confirmed. Cheers -- t signature.asc Description: PGP signature

Causing segmentations fault; Was: Re: No Public Key

2022-11-13 Thread Henning Follmann
> > > > gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No > > Public Key > > > > Debian public keys are listed on web pages for downloads. Here is the link > for download page with checksums and public keys. > > https://www.debian.org/download > &

Re: No Public Key

2022-11-13 Thread Henning Follmann
On Sun, Nov 13, 2022 at 07:27:21PM -0500, Thomas George wrote: > Still strugglng. command suggested returns new key but no user id - skipped > Please do not top post, especially not if answers were posted properly in a chronological way. here is what you should try: gpg --keyserver keyring.debian

Re: No Public Key

2022-11-13 Thread Thomas George
gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No Public Key I thought to skip this step and tried gpg --verify SHA515SUMS.sign.txt debian-11.5.0-amd64-netinst.iso with the result Can't open signed data debian-11.5.0-amd64-netinst.iso Clearly I am making some eleme

Re: No Public Key

2022-11-13 Thread Thomas George
tried gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No Public Key Debian public keys are listed on web pages for downloads. Here is the link for download page with checksums and public keys. https://www.debian.org/download Keys: https://cdimage.debian.org/debian-cd

Re: No Public Key

2022-11-13 Thread Gökşin Akdeniz
Hello, 13.11.2022 22:14 tarihinde Thomas George yazdı: I want to do a new verified instillation of a debian iso. I have the iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No Public Key Debian public keys are

Re: No Public Key

2022-11-13 Thread Darac Marjal
On 13/11/2022 19:14, Thomas George wrote: I want to do a new verified instillation of a debian iso. I have the iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No Public Key I thought to skip this step and tried

No Public Key

2022-11-13 Thread Thomas George
I want to do a new verified instillation of a debian iso. I have the iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No Public Key I thought to skip this step and tried gpg --verify SHA515SUMS.sign.txt debian

Re: Faulty .iso? No public key...

2018-01-09 Thread Jonathan Dowland
What does "apt policy debian-archive-keyring" show? Which version (if any) do you have installed? You could also try "apt install debian-archive-keyring" This should clear up the issues with stretch-updates, but not the virtualbox repository. For that you'll need to find, verify and import the re

Re: Faulty .iso? No public key...

2018-01-09 Thread didier gaumet
Le 09/01/2018 à 07:33, Josh W. a écrit : > I keep having the issue of no public key available and I don’t know what > I should do…. Back up my computer and reinstall or is there a way to > patch it up. I am attaching a file that shows what I am going through. I > ran into all this th

Re: Faulty .iso? No public key...

2018-01-09 Thread Thomas Schmitt
Hi, besides the good advise of John Doe about verifying an ISO, it should be stated that "no public key available" during installation is not a typical sign for a damaged ISO. I'd rather suspect its intentional content being not being correct or maybe the package mirror server

Re: Faulty .iso? No public key...

2018-01-08 Thread john doe
On 1/9/2018 7:33 AM, Josh W. wrote: I keep having the issue of no public key available and I don’t know what I should do…. Back up my computer and reinstall or is there a way to patch it up. I am attaching a file that shows what I am going through. I ran into all this this time will trying to

Faulty .iso? No public key...

2018-01-08 Thread Josh W.
I keep having the issue of no public key available and I don’t know what I should do…. Back up my computer and reinstall or is there a way to patch it up. I am attaching a file that shows what I am going through. I ran into all this this time will trying to install wine and adding to the

Re: "no public key" warning on upgrade to stretch

2017-06-22 Thread Henrique de Moraes Holschuh
On Thu, 22 Jun 2017, Charles E. Blair wrote: >When I type "apt-get upgrade" I get > this message, and things stop: > > W: There is no public key available for the following key IDs: > EF0F382A1A7B6500 > >I hope there is a simple fix. You can ignor

"no public key" warning on upgrade to stretch

2017-06-22 Thread Charles E. Blair
When I type "apt-get upgrade" I get this message, and things stop: W: There is no public key available for the following key IDs: EF0F382A1A7B6500 I hope there is a simple fix.