archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <>
To: Konstantin Ryabitsev <>
Subject: Re: GPG public key Helge Deller
Date: Mon, 7 Mar 2022 20:05:14 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20220307174232.d35s752pthqntwog@meerkat.local>

Hello Konstantin,

On 3/7/22 18:42, Konstantin Ryabitsev wrote:
> On Sun, Mar 06, 2022 at 08:06:37PM +0100, Helge Deller wrote:
> Hmm... this adds a new key that we don't currently have on file for you:
>     pub   rsa4096 2019-11-10 [SC]
>           454482282CD910DBEF3D25F83E5F3D04A7A24603
>     uid                      Helge Deller <>
>     uid                      Helge Deller <>
>     uid                      Helge Deller <>
>     sub   rsa4096 2019-11-10 [E]
>           A66C1BA2340E4BC2471998239FA7FDAEED273BFD
>     sub   ed25519 2019-11-10 [S]
>           BCE9123E1AD29F07C049BBDEF712B510A23A0F5F
> This is the one we have:
>     pub   rsa2048 2012-12-17 [SC]
>           F4CFF4C00BE43CFB5153A06887C9C151B51E3864
>     uid                      Helge Deller <>
>     uid                      Helge Deller <>
>     sub   rsa2048 2012-12-17 [E]
>           2952AE7E354B9C8515D844B3C8698BFB918CE487
>     sub   rsa4096 2013-11-10 [S]
>           969B8CEA9EC2C53635C35F77A183955F30A51241
>     sub   ed25519 2018-06-12 [S]
>           CF9C33A6CB5FD342876C8AC6202A4978DD4FAC5D
> Is it your intention to use the newer key from now on?

I used that newer key already in the last few pull requests to Linus.
I had to generate the new key, because as Debian developer it was required to
provide a rsa4096 key.

Thank you!

      reply	other threads:[~2022-03-07 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 19:06 GPG public key Helge Deller Helge Deller
2022-03-07 17:42 ` Konstantin Ryabitsev
2022-03-07 19:05   ` Helge Deller [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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).