unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Cc: phillip.lord@newcastle.ac.uk, petton.nicolas@gmail.com
Subject: emacs-25.2-x86_64.zip signed by ???
Date: Fri, 19 May 2017 11:47:31 +0200	[thread overview]
Message-ID: <CAEtmmezyNWjbZWMLD0yhW=CUk7JmaSs-uDhGnHsY5vhTkLErsA@mail.gmail.com> (raw)

Hi,

according to Download & installation instructions from
https://www.gnu.org/software/emacs/download.html#windows the
emacs-25.2-x86_64.zip should be signed by Nicolas Petton. To me (if my
interpretation of gpg --verify is correct) it looks likes it is signed by
Phillip Lord.

Would you please clarify this to me, or correct the instructions?

Thanks Bost


$ wget https://ftp.gnu.org/gnu/gnu-keyring.gpg && gpg --import gnu-keyring.gpg
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/home/rsvoboda/.gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
gpg: key 09DF2DC9BE216115: "Francesco Potortì <pot@potorti.it>" not changed
[..]
gpg: key 233587A47C207910: public key "Nicolas Petton
<petton.nicolas@gmail.com>" imported
[..]
gpg: key 969C3BE389DDA6EB: public key "Shigio YAMAGUCHI
<shigio@gnu.org>" imported
gpg: Total number processed: 506
gpg:     skipped PGP-2 keys: 10
gpg:               imported: 131
gpg:              unchanged: 355
gpg:           new user IDs: 9
gpg:            new subkeys: 19
gpg:         new signatures: 689
gpg: no ultimately trusted keys found

$ wget http://gnu.xl-mirror.nl/emacs/windows/emacs-25.2-x86_64.zip
[..]

$ wget http://gnu.xl-mirror.nl/emacs/windows/emacs-25.2-x86_64.zip.sig
[..]

$ gpg --verify emacs-25.2-x86_64.zip.sig emacs-25.2-x86_64.zip
gpg: Signature made Di 25 Apr 2017 18:19:43 CEST
gpg:                using RSA key AC6DD3FFD1D046BD
gpg: Good signature from "Phillip Lord <phillip.lord@newcastle.ac.uk>" [unknown]
gpg:                 aka "Phillip Lord <phillip.lord@russet.org.uk>" [unknown]
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: 8493 0FFB 79B6 45F7 DEA2  9AD0 AC6D D3FF D1D0 46BD



             reply	other threads:[~2017-05-19  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  9:47 Rostislav Svoboda [this message]
2017-05-19 13:35 ` emacs-25.2-x86_64.zip signed by ??? Nicolas Petton
     [not found]   ` <WM!d436413a44834eb761b39e5005b964f317f902ceb1f5fd8f6e6c68cf791460c0ee0547edd97e9a4662c1b4e6b0950b52!@mailhub-mx2.ncl.ac.uk>
2017-05-22 14:53     ` Phillip Lord
2017-05-22 15:37       ` Nicolas Petton
2017-05-22 16:08         ` Rostislav Svoboda

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='CAEtmmezyNWjbZWMLD0yhW=CUk7JmaSs-uDhGnHsY5vhTkLErsA@mail.gmail.com' \
    --to=rostislav.svoboda@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=petton.nicolas@gmail.com \
    --cc=phillip.lord@newcastle.ac.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).