All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Vincent Mailhol <mailhol.vincent@wanadoo.fr>, keys@linux.kernel.org
Subject: Re: Update AB5FEB886DBB99C2
Date: Mon, 10 Feb 2025 11:22:36 -0500	[thread overview]
Message-ID: <20250210-amiable-ruby-toucanet-5d8374@lemur> (raw)
In-Reply-To: <3ie26bbhuzw657fibjyzt4w3tdo5eip6m6nr36b4egzn2lzadi@fv3a4ebsd4f3>

On Mon, Feb 10, 2025 at 01:43:41PM +0100, Uwe Kleine-König wrote:
> > > So let me ask: what type of data are actually synchronized? Is it only
> > > the sub-keys and the expiration dates? Or is there a way to upload the
> > > cross signatures somewhere to have them automatically synchronized in
> > > kernel/pgpkeys.git during the periodic updates?
> > 
> > The keyservers can really only be relied for publishing things like:
> > 
> > - new subkeys
> > - new uids
> > - updated expiry dates
> > 
> > For third-party signature data it's best to send an export to this list.
> 
> Note that keyserver.ubuntu.com still provides 3rd-Party signatures, just
> gpg doesn't import them by default.
> 
> If you really want all that stuff, use:
> 
> 	gpg --refresh --keyserver-options no-self-sigs-only --keyserver keyserver.ubuntu.com

Thank you for the hint! I didn't know that was needed.

However, we'll still probably only use keyservers for key updates, since if a
key is in our keyring, that means we already have sufficient signatures and we
just want updates to things like uids, subkeys and expiration dates.

-K

  reply	other threads:[~2025-02-10 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 15:37 Update AB5FEB886DBB99C2 Vincent Mailhol
2024-11-27 16:02 ` Konstantin Ryabitsev
2024-11-28  5:34   ` Vincent Mailhol
2025-02-10 12:43   ` Uwe Kleine-König
2025-02-10 16:22     ` Konstantin Ryabitsev [this message]
2025-02-10 17:04       ` Uwe Kleine-König

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=20250210-amiable-ruby-toucanet-5d8374@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=keys@linux.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.