From: "Frank Ch. Eigler" <fche@redhat.com>
To: Michael Przybylski <mike@levo.ai>
Cc: elfutils-devel@sourceware.org
Subject: Re: Signing keys for releases?
Date: Fri, 25 Feb 2022 14:42:28 -0500 [thread overview]
Message-ID: <20220225194228.GA2966@redhat.com> (raw)
In-Reply-To: <0588587cc4efb2a48ee4746f5da9865bc1bb0380.camel@levo.ai>
Hi -
> 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
- FChE
next prev parent reply other threads:[~2022-02-25 19:42 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 [this message]
2022-02-25 21:21 ` Mark Wielaard
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=20220225194228.GA2966@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--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).