bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: announce-gen and OpenPGP key servers
Date: Sun, 1 Aug 2021 17:47:19 +0200	[thread overview]
Message-ID: <07a9c597-5c07-ec61-7d3c-32b503063be2@bernhard-voelker.de> (raw)
In-Reply-To: <87y29sf65o.fsf@latte.josefsson.org>

On 7/27/21 11:38 AM, Simon Josefsson via Gnulib discussion list wrote:
> Let's discuss and see what we can do.
Isn't this what the "release GPG keys" on Savannah are for?

Each project maintainer can set them up correctly under "Edit public info":
  "https://savannah.gnu.org/project/admin/editgroupinfo.php?group=${PROJECT}"

The result can be downloaded by users for verification:
  "https://savannah.gnu.org/project/release-gpgkeys.php?group=${PROJECT}&download=1"
e.g. coreutils':
  "https://savannah.gnu.org/project/release-gpgkeys.php?group=coreutils&download=1"

Downstream sometimes use them, e.g. SUSE and openSUSE are verifying the keys
on their Open Build Service.

Have a nice day,
Berny


  parent reply	other threads:[~2021-08-01 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  9:38 announce-gen and OpenPGP key servers Simon Josefsson via Gnulib discussion list
2021-07-27 18:48 ` Paul Eggert
2021-07-28  1:57 ` Jim Meyering
2021-08-03 15:40   ` Simon Josefsson via Gnulib discussion list
2021-08-03 17:52     ` Jim Meyering
2021-08-03 19:20       ` Simon Josefsson via Gnulib discussion list
2021-08-03 19:25         ` Paul Eggert
2021-08-03 23:51           ` Jim Meyering
2021-08-04  9:19             ` Simon Josefsson via Gnulib discussion list
2021-08-01 15:47 ` Bernhard Voelker [this message]
2021-08-02 10:09   ` Simon Josefsson via Gnulib discussion list

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07a9c597-5c07-ec61-7d3c-32b503063be2@bernhard-voelker.de \
    --to=mail@bernhard-voelker.de \
    --cc=bug-gnulib@gnu.org \
    --cc=simon@josefsson.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 read-only IMAP folder(s) and NNTP newsgroup(s).