public inbox for keys@kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: keys@linux.kernel.org
Subject: Re: New GPG key
Date: Tue, 20 Aug 2024 14:52:47 +1000	[thread overview]
Message-ID: <874j7fu76o.fsf@mail.lhotse> (raw)
In-Reply-To: <20240819-majestic-logical-galago-dcd95a@lemur>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Mon, Aug 19, 2024 at 02:24:22PM GMT, Michael Ellerman wrote:
>> Hi,
>> 
>> Can you please add my new GPG key to the repo.
>
> For the record, can you follow up with the reason why you're replacing your
> main key?

My old key is a combined signing/certification key, and it wasn't stored
offline. AFAIK it's still secure, but I wanted to start fresh.

My new key was generated following the docs you wrote and has sub keys
etc. with the master key and another signing key stored offline.

cheers

  reply	other threads:[~2024-08-20  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  4:24 New GPG key Michael Ellerman
2024-08-19 15:00 ` Konstantin Ryabitsev
2024-08-20  4:52   ` Michael Ellerman [this message]
2024-08-21 15:17     ` 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=874j7fu76o.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=keys@linux.kernel.org \
    --cc=konstantin@linuxfoundation.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