all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Vagrant Cascadian" <vagrant@debian.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Maxime Devos" <maximedevos@telenet.be>
Cc: Tanguy LE CARROUR <tanguy@bioneland.org>, guix-devel@gnu.org
Subject: Re: Finding a “good” OpenPGP key server
Date: Tue, 31 May 2022 19:44:33 +0200	[thread overview]
Message-ID: <8735gpbnr2.fsf@gmail.com> (raw)
In-Reply-To: <878rqhd9i6.fsf@contorta>

Hi,

On mar., 31 mai 2022 at 08:09, Vagrant Cascadian <vagrant@debian.org> wrote:

> Or keep some keyrings in a git repo, if we want to keep the keys
> somewhat restricted to committers... a major problem of the public
> keyserver network is/was the ability for anyone to update or add any key
> for anybody.
>
> We've already got the keyring branch in guix.git, maybe adding an
> upstream-keys branch wouldn't be madness? Or a separate git
> repository. And then you could get it archived at software heritage or
> archive.org or whatever trivially.

I have not closely followed all the thread.  Just to mention that the
upstream-keys branch or separate Git repository using Software Heritage
or archive.org as backup require some tests for complete robustness.

I have in mind some examples where it is not “trivial” to get back from
SWH; because their cooking vault is slow, because the repo is big or
complex, etc.

That’s said, I agree that Git seems the easiest for preserving keyrings.


Cheers,
simon


  reply	other threads:[~2022-05-31 18:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  8:17 Error updating gnurl Tanguy LE CARROUR
2022-04-18 20:24 ` Finding a “good” OpenPGP key server Ludovic Courtès
2022-04-21 17:15   ` Tanguy LE CARROUR
2022-04-28  7:35     ` Ludovic Courtès
2022-04-29 19:11   ` Philip McGrath
2022-05-02  7:21     ` Tanguy LE CARROUR
2022-05-23 14:43       ` Ludovic Courtès
2022-05-23 16:19   ` Maxime Devos
2022-05-30 15:34     ` Ludovic Courtès
2022-05-31  7:55       ` Tanguy LE CARROUR
2022-05-31  8:44       ` Maxime Devos
2022-06-01 16:31         ` Ludovic Courtès
2022-05-31 15:09       ` Vagrant Cascadian
2022-05-31 17:44         ` zimoun [this message]
2022-06-01 16:32         ` Ludovic Courtès

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=8735gpbnr2.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=tanguy@bioneland.org \
    --cc=vagrant@debian.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.