public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] GPG key refresh
Date: Mon, 14 Dec 2020 11:17:55 -0800	[thread overview]
Message-ID: <CAAr7Pr-uzdLafocoA6bvEcAbDVuWnnjinCqqbH27gEncYJL-2g@mail.gmail.com> (raw)
In-Reply-To: <3789ea75-1287-f225-ed58-11d26a440cb0@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

antarus@woodpecker ~ $ gpg --keyserver hkps://keys.gentoo.org --search-keys
1C49724D229E93A2
gpg: data source: https://[2001:470:ea4a:1:230:48ff:fef8:9fdc]:443
(1)     Michael Orlitzky <mjo@gentoo.org>
       Michael Orlitzky <michael@orlitzky.com>
         4096 bit RSA key 1C49724D229E93A2, created: 2010-03-17, expires:
2020-12-26
Keys 1-1 of 1 for "1C49724D229E93A2".  Enter number(s), N)ext, or Q)uit > q
gpg: error searching keyserver: Operation cancelled
gpg: keyserver search failed: Operation cancelled

I think you need to push to hkps://keys.gentoo.org

-A

On Mon, Dec 14, 2020 at 11:00 AM Michael Orlitzky <mjo@gentoo.org> wrote:

> I'm still getting this,
>
>    $ git push --signed
>    ...
>    remote: 1C49724D229E93A2 [Michael Orlitzky <mjo@gentoo.org>] [E]
>    expire:short Expiration date is too close, please renew (is 2020-12-26
>    23:30:47, less than 14 days)
>    remote: 1C49724D229E93A2:6F48D3DA05C2DADB [Michael Orlitzky
>    <mjo@gentoo.org>] [E] expire:short Expiration date is too close,
>    please renew (is 2020-12-26 23:31:43, less than 14 days)
>
> over a week after I've renewed my keys. The answer I get back from the
> keyserver(s) looks OK:
>
>    $ gpg --search-keys 0x6F48D3DA05C2DADB
>    gpg: data source: http://85.25.207.23:11371
>    (1)   Michael Orlitzky <mjo@gentoo.org>
>          Michael Orlitzky <michael@orlitzky.com>
>            4096 bit RSA key 0x1C49724D229E93A2, created: 2010-03-17,
>            expires: 2022-12-05
>
>
> Did I forget a step? How long should it take for infra to refresh?
>
>

[-- Attachment #2: Type: text/html, Size: 2833 bytes --]

  reply	other threads:[~2020-12-14 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 18:59 [gentoo-dev] GPG key refresh Michael Orlitzky
2020-12-14 19:17 ` Alec Warner [this message]
2020-12-14 19:41   ` Michael Orlitzky
2020-12-15 15:27     ` Thomas Deutschmann
2020-12-15 15:44       ` Michael Orlitzky
2020-12-15 15:49       ` Michael Orlitzky
2020-12-15 16:11         ` Thomas Deutschmann
2020-12-15 16:16           ` Michael Orlitzky
2020-12-16  4:37             ` Aaron W. Swenson
2020-12-16  8:01               ` Michał Górny
2020-12-17  4:48                 ` desultory
2020-12-17 18:28                   ` Mike Gilbert
2020-12-17 19:23                     ` Michał Górny
2020-12-17 18:35                 ` Mike Gilbert
2020-12-17 19:22                   ` Michał Górny
2020-12-14 19:24 ` Cédric Krier

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=CAAr7Pr-uzdLafocoA6bvEcAbDVuWnnjinCqqbH27gEncYJL-2g@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox