all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Public key for verifying emacs sources?
Date: Sun, 18 Jul 2021 15:05:03 +0300	[thread overview]
Message-ID: <83o8az7rps.fsf@gnu.org> (raw)
In-Reply-To: <YPQSn3XSMPgB41S5@protected.localdomain> (message from Jean Louis on Sun, 18 Jul 2021 14:38:07 +0300)

> Date: Sun, 18 Jul 2021 14:38:07 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: help-gnu-emacs@gnu.org
> 
> * Eli Zaretskii <eliz@gnu.org> [2021-07-18 10:02]:
> > > Date: Sat, 17 Jul 2021 21:44:31 -0400
> > > From: Steve Revilak <steve@srevilak.net>
> > > 
> > > Where can I find a copy of the signing key, so I can verify the source
> > > distribution I've downloaded?
> > 
> > Download the latest gnu-keyring.gpg from
> > https://ftp.gnu.org/gnu/gnu-keyring.gpg, then type:
> > 
> >    gpg --import gnu-keyring.gpg
> > 
> > Then try verifying the signature again.
> 
> Me too, I have done the import and I see large number of keys. While
> it is good that keys are distributed from official GNU.org server,
> there is no published assurance that GNU project verified each key to
> belong to the person it should belong. Thus one shall not forget
> security depends on the weakest part.

Please take this up with the GNU FTP site maintainers.  I didn't
upload my key to any place, I sent them my key and asked for upload
rights.  I don't know what they did with the key.

This issue doesn't belong on this forum anyway.



  reply	other threads:[~2021-07-18 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18  1:44 Public key for verifying emacs sources? Steve Revilak
2021-07-18  7:00 ` Eli Zaretskii
2021-07-18 11:38   ` Jean Louis
2021-07-18 12:05     ` Eli Zaretskii [this message]
2021-07-18 14:08   ` Steve Revilak

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=83o8az7rps.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.