public inbox for keys@kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: keys@linux.kernel.org
Subject: Re: Keys for Stephen Brennan
Date: Mon, 22 Aug 2022 09:56:36 -0700	[thread overview]
Message-ID: <877d30kyij.fsf@oracle.com> (raw)
In-Reply-To: <20220822150046.xwlk6j42r2gxpw4k@meerkat.local>

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

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Fri, Aug 19, 2022 at 05:10:56PM -0700, Stephen Brennan wrote:
>> Hello,
>> 
>> Adding my key with identities for stephen@brennan.io and
>> stephen.s.brennan@oracle.com, both of which I use. Should be attached
>> with relevant signatures.
>
> Hello:
>
> There are no signatures on the attached key other than self-sigs.
>
> 	$ gpg --list-packets /tmp/inc.gpg | grep ':signature'
> 	:signature packet: algo 1, keyid 2EADC69438E476F9
> 	:signature packet: algo 1, keyid 2EADC69438E476F9
> 	:signature packet: algo 1, keyid 2EADC69438E476F9
> 	:signature packet: algo 1, keyid 2EADC69438E476F9
> 	:signature packet: algo 1, keyid 2EADC69438E476F9

I guess I missed all the changes to keyservers not distributing third
party signatures anymore! I just assumed that a "--recv-key" would get
my signatures but I need to manually copy the exported key these days.

I've attached re-exported key with third-party signatures.

Thanks,
Stephen

[-- Attachment #2: key.asc --]
[-- Type: application/pgp-keys, Size: 9293 bytes --]

  reply	other threads:[~2022-08-22 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20  0:10 Keys for Stephen Brennan Stephen Brennan
2022-08-22 15:00 ` Konstantin Ryabitsev
2022-08-22 16:56   ` Stephen Brennan [this message]
2022-08-22 17:16     ` 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=877d30kyij.fsf@oracle.com \
    --to=stephen.s.brennan@oracle.com \
    --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