From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Richard Kettlewell <rjk@terraraq.uk>, 25572@debbugs.gnu.org
Subject: bug#25572: Signatures on Emacs windows .zip files
Date: Sun, 29 Jan 2017 21:14:46 -0000 [thread overview]
Message-ID: <41759f91c06b857e642d6a5394db2de0.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <83d1f5y67j.fsf@gnu.org>
On Sun, January 29, 2017 8:14 pm, Eli Zaretskii wrote:
>> From: Richard Kettlewell <rjk@terraraq.uk>
>> Date: Sun, 29 Jan 2017 11:48:55 +0000
>>
>>
>> $ gpg2 --verify emacs-25.1-2-x86_64-w64-mingw32.zip.sig
>> gpg: Signature made 11/29/16 19:54:09 GMT Standard Time using DSA key ID
>> 60C3B396
>> gpg: Good signature from "Phillip Lord <phillip.lord@russet.org.uk>"
>> gpg: aka "Phillip Lord <p.lord@russet.org.uk>"
>> gpg: aka "Phillip Lord <p.lord@hgmp.mrc.ac.uk>"
>> gpg: aka "Phillip Lord <phillip.lord@newcastle.ac.uk>"
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg: There is no indication that the signature belongs to the
>> owner. Primary key fingerprint: 8352 2404 7598 ECBC 61A1 DA34 5FE9 658D
>> 60C3 B396
>>
>
> That's because the zip files with Windows binaries were produced by
> Phillip.
>
>
> Why is that a bug?
>
I think it's a flaw with the website. It needs both our keys on.
next prev parent reply other threads:[~2017-01-29 21:14 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 [this message]
2017-01-30 22:32 ` Glenn Morris
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=41759f91c06b857e642d6a5394db2de0.squirrel@cloud103.planethippo.com \
--to=phillip.lord@russet.org.uk \
--cc=25572@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).