GNU bug report logs - #41266
Suggested command to import key does not work on debian

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41266 in the body.
You can then email your comments to 41266 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: bug-guix <at> gnu.org
Subject: Suggested command to import key does not work on debian
Date: Thu, 14 May 2020 12:28:11 -0400

Hi,

I just installed a debian VM to test changes in the install script and found this issue when running the installer script:

First it fails because it cannot find the public key and suggests running:

wget … -q0 - | gpg --import

-q0 does not work with debian's wget, but -O works.

Aftcr importing the key, the script still complains it cannot find it. Re-running the same command with "sudo" in front of the gpg import command re-imports the key and the script is then able to find it.

My guess is that the first import imported the key in my user's keyring, but the script looks in root's keyring. The second attempt added the key to root's keyring.

Message #8 received at 41266 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 41266 <at> debbugs.gnu.org
Subject: Re: bug#41266: Suggested command to import key does not work on debian
Date: Thu, 14 May 2020 19:27:07 +0200

Hi Julien,

> First it fails because it cannot find the public key and suggests running:
>
> wget … -q0 - | gpg --import
>
> -q0 does not work with debian's wget, but -O works.

The installer script does not display this command.  There is no zero in
the wget commands.

> Aftcr importing the key, the script still complains it cannot find
> it. Re-running the same command with "sudo" in front of the gpg import
> command re-imports the key and the script is then able to find it.
>
> My guess is that the first import imported the key in my user's
> keyring, but the script looks in root's keyring. The second attempt
> added the key to root's keyring.

Yes, this is correct.  Since the installer script runs as root the key
import also needs to be done as root to affect the root user’s keyring.

-- 
Ricardo

Message #11 received at 41266 <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: 41266 <at> debbugs.gnu.org
Subject: Re: bug#41266: Suggested command to import key does not work on debian
Date: Sun, 17 May 2020 21:25:54 +0200

Le Thu, 14 May 2020 12:28:11 -0400,
Julien Lepiller <julien <at> lepiller.eu> a écrit :

> Hi,
> 
> I just installed a debian VM to test changes in the install script
> and found this issue when running the installer script:
> 
> First it fails because it cannot find the public key and suggests
> running:
> 
> wget … -q0 - | gpg --import
> 
> -q0 does not work with debian's wget, but -O works.
> 
> Aftcr importing the key, the script still complains it cannot find
> it. Re-running the same command with "sudo" in front of the gpg
> import command re-imports the key and the script is then able to find
> it.
> 
> My guess is that the first import imported the key in my user's
> keyring, but the script looks in root's keyring. The second attempt
> added the key to root's keyring.
> 

Forget the wget thing, it's my fault for not reading it properly. The
gpg command still needs to be run with sudo on at least fedora and
debian.

Message #14 received at 41266 <at> debbugs.gnu.org (full text, mbox):

From: Bengt Richter <bokr <at> bokr.com>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 41266 <at> debbugs.gnu.org
Subject: Re: bug#41266: Suggested command to import key does not work on debian
Date: Sun, 17 May 2020 21:48:02 +0200

Hi,

On +2020-05-17 21:25:54 +0200, Julien Lepiller wrote:
> Le Thu, 14 May 2020 12:28:11 -0400,
> Julien Lepiller <julien <at> lepiller.eu> a écrit :
> 
> > Hi,
> > 
> > I just installed a debian VM to test changes in the install script
> > and found this issue when running the installer script:
> > 
> > First it fails because it cannot find the public key and suggests
> > running:
> > 
> > wget … -q0 - | gpg --import
> > 
> > -q0 does not work with debian's wget, but -O works.
> > 
> > Aftcr importing the key, the script still complains it cannot find
> > it. Re-running the same command with "sudo" in front of the gpg
> > import command re-imports the key and the script is then able to find
> > it.
> > 
> > My guess is that the first import imported the key in my user's
> > keyring, but the script looks in root's keyring. The second attempt
> > added the key to root's keyring.
> > 
> 
> Forget the wget thing, it's my fault for not reading it properly. The
> gpg command still needs to be run with sudo on at least fedora and
> debian.
> 
> 
>
If the problem is actually expired keys vs nonexistent,
gpg --refresh-keys
might be worth trying.


-- 
Regards,
Bengt Richter

Message #19 received at 41266-done <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 41266-done <at> debbugs.gnu.org
Subject: Re: bug#41266: Suggested command to import key does not work on debian
Date: Wed, 28 Oct 2020 18:40:39 +0100

Hi,

On Sun, 17 May 2020 at 21:25, Julien Lepiller <julien <at> lepiller.eu> wrote:

> Forget the wget thing, it's my fault for not reading it properly. The
> gpg command still needs to be run with sudo on at least fedora and
> debian.

Now, the binary install script “guix-install.sh” displays:

  echo "  wget 'https://sv.gnu.org/people/viewgpg.php?user_id=15145' -qO - | sudo -i gpg --import -"

Therefore, it is fine, right?  I am closing but feel free to reopen if I
misread or miss something.


Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.