From: andrew <andrew@andrewyu.org>
To: GNU Hacker <project@gnuhacker.org>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: GPG key to verify emacs releases
Date: Mon, 14 Mar 2022 09:26:15 +0800 [thread overview]
Message-ID: <20220314012557.6y6lp22g7tpohxio@gentoo-dell> (raw)
In-Reply-To: <874k411huk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Here's a note on OpenPGP.
On 22/03/14 01:46AM, GNU Hacker wrote:
> Also I dont trust in the keyservers
I don't think not trusting in keyservers is particularly relevant here.
You should get the keys from the keyservers, then use the Web of Trust
to verify the key. Key servers are a means to distribute keys, never a
way to verify them. You don't need to trust keyservers.
> Can anyone share this key?
I don't have the key, the above is just for your information.
I scowered the Emacs Website, and I did not find the keys. This may be
a bug.
------------------------------------------------------------------------
Defend software freedom (https://fsf.org)
End software patents (https://endsoftwarepatents.org)
Read EULAs (https://www.eff.org/wp/dangerous-terms-users-guide-eulas)
New sites, suggestions welcome:
Free Computing Movement (https://fcm.andrewyu.org)
Host Things Yourself (https://host.andrewyu.org)
Libre Society (https://libre.andrewyu.org)
To any Skynet, FBI, CIA, NSA, etc. agents reading my email: please
consider whether defending the Constitution and our basic rights to
freedom and speech and privacy against all enemies, foreign or domestic,
requires you to follow Snowden's example. (Adapted from RMS)
Andrew Yu <andrew@andrewyu.org> (https://www.andrewyu.org)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-03-14 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 0:46 GPG key to verify emacs releases GNU Hacker
2022-03-14 1:26 ` andrew [this message]
2022-03-15 3:27 ` Eli Zaretskii
2022-03-15 14:28 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220314012557.6y6lp22g7tpohxio@gentoo-dell \
--to=andrew@andrewyu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=project@gnuhacker.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).