From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Michael Przybylski <mike@levo.ai>, elfutils-devel@sourceware.org
Subject: Re: Signing keys for releases?
Date: Fri, 25 Feb 2022 22:21:12 +0100 [thread overview]
Message-ID: <20220225212112.GA17594@gnu.wildebeest.org> (raw)
In-Reply-To: <20220225194228.GA2966@redhat.com>
Hi,
On Fri, Feb 25, 2022 at 02:42:28PM -0500, Frank Ch. Eigler via Elfutils-devel wrote:
> > Could you please point me toward the PGP/GPG public keys necessary to
> > validate the elfutils release tarballs against their .sig files?
>
> Try these:
>
> https://sourceware.org/elfutils/ftp/gpgkey-1AA44BE649DE760A.gpg
> https://sourceware.org/elfutils/ftp/gpgkey-5C1D1AA44BE649DE760A.gpg
There is also the GPG-KEY file inside the tar.gz dists (obviously then
you have to unpack the tarbal first to get at that before you can
check it...)
But you can also get it from git:
https://sourceware.org/git/?p=elfutils.git;a=blob_plain;f=GPG-KEY;hb=HEAD
Cheers,
Mark
prev parent reply other threads:[~2022-02-25 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 18:54 Michael Przybylski
2022-02-25 19:42 ` Frank Ch. Eigler
2022-02-25 21:21 ` Mark Wielaard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220225212112.GA17594@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mike@levo.ai \
/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).