all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: GWL 0.3.0 released
Date: Thu, 11 Feb 2021 22:59:28 +0100	[thread overview]
Message-ID: <20210211215928.GA6833@LionPure> (raw)
In-Reply-To: <87ft22qr17.fsf@elephly.net>

On +2021-02-11 21:37:56 +0100, Ricardo Wurmus wrote:
> 
> Bengt Richter <bokr@bokr.com> writes:
> 
> > gpg --verify gwl-0.3.0.tar.gz.sig
> > gpg: assuming signed data in 'gwl-0.3.0.tar.gz'
> > gpg: Signature made Sat 06 Feb 2021 09:28:59 PM CET
> > gpg:                using RSA key BCA689B636553801C3C62150197A5888235FACAC
> > gpg: Good signature from "Ricardo Wurmus (Work) <ricardo.wurmus@mdc-berlin.de>" [expired]
> > gpg:                 aka "rekado <rekado@elephly.net>" [expired]
> > ┌──────────────────────────────────┐
> > │ gpg: Note: This key has expired! │
> > └──────────────────────────────────┘
> 
> You should get a fresh key from keys.openpgp.org
> Its expiry is regularly extended.
>
Thanks for all your Fosdem/guix work first of all, but I expected

--8<---------------cut here---------------start------------->8---
[17:29 ~/bs]$ gpg --keyserver keys.gnupg.net --recv-keys BCA689B636553801C3C62150197A5888235FACAC
gpg: key 197A5888235FACAC: 16 signatures not checked due to missing keys
┌───────────────────────────────────────────────────────────────────────────────────────────────┐
│ gpg: key 197A5888235FACAC: "Ricardo Wurmus (Work) <ricardo.wurmus@mdc-berlin.de>" not changed │
└───────────────────────────────────────────────────────────────────────────────────────────────┘
gpg: Total number processed: 1
gpg:              unchanged: 1
--8<---------------cut here---------------end--------------->8---

to give me an updated key, and am left wondering why it didn't :)
It seems I have a wrong default for keyserver:

--8<---------------cut here---------------start------------->8---
[22:21 ~/bs]$ gpg --refresh-keys
gpg: refreshing 6 keys from hkp://hkps.pool.sks-keyservers.net
gpg: key 197A5888235FACAC: 14 signatures not checked due to missing keys
┌───────────────────────────────────────────────────────────────────────────────────────────────┐
│ gpg: key 197A5888235FACAC: "Ricardo Wurmus (Work) <ricardo.wurmus@mdc-berlin.de>" not changed │
└───────────────────────────────────────────────────────────────────────────────────────────────┘
--8<---------------cut here---------------end--------------->8---


Maybe the original advice for getting a key should be extended with the
fresh key advice above (preferably the literal gpg command line, my guess re that boxed below).
This seems to do it:
┌───────────────────────────────────────────────────────────────────────────────────────┐
│ gpg --recv-keys BCA689B636553801C3C62150197A5888235FACAC --keyserver keys.openpgp.org │
└───────────────────────────────────────────────────────────────────────────────────────┘
(though my first try was "gpg --refresh-keys --keyserver keys.openpgp.org"
which only found you for the keys I have).

--8<---------------cut here---------------start------------->8---
[22:44 ~/bs]$ gpg --recv-keys BCA689B636553801C3C62150197A5888235FACAC --keyserver keys.openpgp.org
gpg: Note: '--keyserver' is not considered an option
gpg: "--keyserver" not a key ID: skipping
gpg: "keys.openpgp.org" not a key ID: skipping
gpg: key 197A5888235FACAC: 16 signatures not checked due to missing keys
gpg: key 197A5888235FACAC: "Ricardo Wurmus (Work) <ricardo.wurmus@mdc-berlin.de>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
--8<---------------cut here---------------end--------------->8---

Now gpg --verify works \o/ :)

> 
> Ricardo
-- 
Regards,
Bengt Richter


      reply	other threads:[~2021-02-11 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 23:07 GWL 0.3.0 released Ricardo Wurmus
2021-02-10 21:05 ` Ludovic Courtès
2021-02-11 16:37   ` Bengt Richter
2021-02-11 19:03     ` Cook, Malcolm
2021-02-11 20:04       ` Leo Famulari
2021-02-11 20:37     ` Ricardo Wurmus
2021-02-11 21:59       ` Bengt Richter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210211215928.GA6833@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.