public inbox for keys@kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>, keys@linux.kernel.org
Subject: Re: key AB4800A62DB9F73A (Seth Forshee) expired
Date: Mon, 16 Feb 2026 18:49:30 -0600	[thread overview]
Message-ID: <aZO7Gga9RCRIidFg@ubuntu-x1> (raw)
In-Reply-To: <20260213-magic-rare-termite-bb1cb4@lemur>

On Fri, Feb 13, 2026 at 04:38:06PM -0500, Konstantin Ryabitsev wrote:
> On Tue, Feb 03, 2026 at 09:12:54AM -0600, Seth Forshee wrote:
> > > this is a quick FYI that your PGP certificate AB4800A62DB9F73A in the
> > > version that is tracked in
> > > https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/keys/AB4800A62DB9F73A.asc
> > > expired earlier this month.
> > > 
> > > If you don't use this key for kernel work any more, please let us know.
> > > Otherwise I suggest to expand the key's expiry date by doing e.g.:
> > > 
> > > 	gpg --quick-set-expire 2ABCA7498D83E1D32D51D3B5AB4800A62DB9F73A 2y
> > > 	gpg --keyserver hkps://keys.openpgp.org/ --send-key 2ABCA7498D83E1D32D51D3B5AB4800A62DB9F73A
> > > 
> > > to extend the expiry by 2 years.
> > 
> > Ah, I guess I forgot to put a reminder on my calendar. I'll get it
> > updated. Thanks for the heads up!
> 
> Hello!
> 
> Note that it's still expired. 

Yes, my apologies. Updated now.

Thanks!
Seth

  reply	other threads:[~2026-02-17  0:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  9:20 key AB4800A62DB9F73A (Seth Forshee) expired Uwe Kleine-König
2026-02-03 15:12 ` Seth Forshee
2026-02-13 21:38   ` Konstantin Ryabitsev
2026-02-17  0:49     ` Seth Forshee [this message]
2026-02-17 14:20       ` Konstantin Ryabitsev

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=aZO7Gga9RCRIidFg@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=keys@linux.kernel.org \
    --cc=mricon@kernel.org \
    --cc=u.kleine-koenig@baylibre.com \
    /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