From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Bernhard Voelker <mail@bernhard-voelker.de>, bug-gnulib@gnu.org
Subject: Re: announce-gen and OpenPGP key servers
Date: Mon, 02 Aug 2021 12:09:06 +0200 [thread overview]
Message-ID: <f9163cf4da0bec13ec642643f46fbc8a1d06ab63.camel@josefsson.org> (raw)
In-Reply-To: <07a9c597-5c07-ec61-7d3c-32b503063be2@bernhard-voelker.de>
sön 2021-08-01 klockan 17:47 +0200 skrev Bernhard Voelker:
> 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.
Right, thanks for pointing that out. It can be used in some
situations. One concern is that the set of keys trusted for uploads to
ftp.gnu.org is a a different set of keys, and not all GNU projects use
Savannah.
/Simon
prev parent reply other threads:[~2021-08-02 10:09 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
2021-08-02 10:09 ` Simon Josefsson via Gnulib discussion list [this message]
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=f9163cf4da0bec13ec642643f46fbc8a1d06ab63.camel@josefsson.org \
--to=bug-gnulib@gnu.org \
--cc=mail@bernhard-voelker.de \
--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).