From: Glenn Morris <rgm@gnu.org>
To: "Phillip Lord" <phillip.lord@russet.org.uk>
Cc: Richard Kettlewell <rjk@terraraq.uk>, 25572@debbugs.gnu.org
Subject: bug#25572: Signatures on Emacs windows .zip files
Date: Mon, 30 Jan 2017 17:32:31 -0500 [thread overview]
Message-ID: <3nk29cch6o.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <41759f91c06b857e642d6a5394db2de0.squirrel@cloud103.planethippo.com> (Phillip Lord's message of "Sun, 29 Jan 2017 21:14:46 -0000")
"Phillip Lord" wrote:
> I think it's a flaw with the website. It needs both our keys on.
It is it actually useful to list gpg keys on
https://www.gnu.org/software/emacs/download.html, or is it just another
place that's likely to get out-of-date?
Historically, the "GNU keyring" has frequently been outdated and hard to
get updated (it should be automatic but clearly isn't), so I don't know
if linking to that is a good idea. (Personally I fail to see much value
in a keyring stored on the same ftp server as the files. If a Bad Person
can mess with the latter, why not the former?)
next prev parent reply other threads:[~2017-01-30 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 11:48 bug#25572: Signatures on Emacs windows .zip files Richard Kettlewell
2017-01-29 20:14 ` Eli Zaretskii
2017-01-29 20:36 ` Richard Kettlewell
2017-01-29 21:14 ` Phillip Lord
2017-01-30 22:32 ` Glenn Morris [this message]
2017-02-06 10:37 ` Phillip Lord
2017-02-06 13:09 ` Nicolas Petton
2017-02-07 4:37 ` Glenn Morris
2017-01-29 20:56 ` Phillip Lord
2017-01-29 21:37 ` Richard Kettlewell
2017-02-06 13:04 ` Nicolas Petton
2017-11-19 14:11 ` Richard Kettlewell
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=3nk29cch6o.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25572@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=rjk@terraraq.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).