keys.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: keys@linux.kernel.org
Subject: Re: tj@kernel.org
Date: Tue, 7 Jun 2022 10:49:39 -1000	[thread overview]
Message-ID: <Yp+54z+jHbBrsv49@slm.duckdns.org> (raw)
In-Reply-To: <20220607202824.5nhr4aeii2s4q2ds@meerkat.local>

Hello, Konstantin.

On Tue, Jun 07, 2022 at 04:28:24PM -0400, Konstantin Ryabitsev wrote:
> On Tue, Jun 07, 2022 at 10:00:46AM -1000, Tejun Heo wrote:
> > -----BEGIN PGP PUBLIC KEY BLOCK-----
> 
> There are no signatures on this key, so we cannot accept it into the keyring.
> Did you lose access to your previous key, 19F81DC583926170 ?

Yeah, many years ago. I got signatures from Kyle, Jakub and Paul.

  htejun@slm ~ (master)> gpg --list-signatures
  /home/htejun/.gnupg/pubring.kbx
  -------------------------------
  pub   rsa4096 2022-05-25 [SC]
        697C63013E65270255EBC2608744DC1EB26B5A9A
  uid           [ultimate] Tejun Heo <tj@kernel.org>
  sig 3        8744DC1EB26B5A9A 2022-05-25  Tejun Heo <tj@kernel.org>
  sub   rsa4096 2022-05-25 [E]
  sig          8744DC1EB26B5A9A 2022-05-25  Tejun Heo <tj@kernel.org>
  sub   ed25519 2022-06-07 [S]
  sig          8744DC1EB26B5A9A 2022-06-07  Tejun Heo <tj@kernel.org>

  pub   rsa4096 2011-10-17 [SC]
        F402A49CEE3B80C4E4E6C37F460EF99392319BC6
  uid           [ unknown] Kyle McMartin <kyle@mcmartin.ca>
  sig 3        460EF99392319BC6 2012-01-26  Kyle McMartin <kyle@mcmartin.ca>
  uid           [ unknown] Kyle McMartin <kmcmarti@redhat.com>
  sig 3        460EF99392319BC6 2012-02-02  Kyle McMartin <kyle@mcmartin.ca>
  sub   rsa4096 2011-10-17 [E]
  sig          460EF99392319BC6 2011-10-17  Kyle McMartin <kyle@mcmartin.ca>

  pub   rsa4096 2017-12-22 [SC] [expires: 2024-06-10]
        EA33C0F88D6E82620103885731466D6DFE5222BB
  uid           [ unknown] Jakub Kicinski <kuba@kernel.org>
  sig 3        31466D6DFE5222BB 2020-10-12  Jakub Kicinski <kuba@kernel.org>
  uid           [ unknown] Jakub Kicinski <kubakici@wp.pl>
  sig 3        31466D6DFE5222BB 2019-06-12  Jakub Kicinski <kuba@kernel.org>
  sig 3        31466D6DFE5222BB 2017-12-22  Jakub Kicinski <kuba@kernel.org>
  sub   rsa4096 2017-12-22 [E] [expires: 2024-06-10]
  sig          31466D6DFE5222BB 2019-06-12  Jakub Kicinski <kuba@kernel.org>

  pub   rsa4096 2011-10-05 [SC]
        6CAED4ACCF91048AC2A158899EBF12F372D9FB8C
  uid           [ unknown] Paul E. McKenney <paulmck@linux.vnet.ibm.com>
  sig 3        9EBF12F372D9FB8C 2011-10-05  Paul E. McKenney <paulmck@linux.vnet.ibm.com>
  sub   rsa4096 2011-10-05 [E]
  sig          9EBF12F372D9FB8C 2011-10-05  Paul E. McKenney <paulmck@linux.vnet.ibm.com>

and they're also on the ubuntu keyserver

  http://keyserver.ubuntu.com/pks/lookup?search=0x697C63013E65270255EBC2608744DC1EB26B5A9A&fingerprint=on&op=index

My grasp of gpg is really flimsy. Should I get more signatures or do
something differently to send you the signatures?

Thank you.

-- 
tejun

  reply	other threads:[~2022-06-07 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 20:00 tj@kernel.org Tejun Heo
2022-06-07 20:28 ` tj@kernel.org Konstantin Ryabitsev
2022-06-07 20:49   ` Tejun Heo [this message]
2022-06-07 21:29     ` tj@kernel.org Konstantin Ryabitsev
2022-06-07 21:29       ` tj@kernel.org Tejun Heo

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=Yp+54z+jHbBrsv49@slm.duckdns.org \
    --to=tj@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).