unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Third <alan@idiocy.org>
Cc: 35060@debbugs.gnu.org, Andrew Luke Nesbit <ullbeking@andrewnesbit.org>
Subject: bug#35060: 26.1; Incorrect OpenPGP key on Emacs site
Date: Wed, 22 Sep 2021 23:50:35 +0200	[thread overview]
Message-ID: <87czp0qnys.fsf@gnus.org> (raw)
In-Reply-To: <CABGBtwkCoyFkjH9ViAHmPgtuF7fMBwVQNZgnXFSD=brWmfEfwQ@mail.gmail.com> (Alan Third's message of "Tue, 2 Apr 2019 14:59:25 +0100")

Alan Third <alan@idiocy.org> writes:

> On Tue, 2 Apr 2019, 07:13 Andrew Luke Nesbit,
> <ullbeking@andrewnesbit.org> wrote:
>
>  The user is instructed to √erify the signature of the download, but the
>  information about who it's signed by is misleading.  The key that signs
>  the signature for releases >= 26.1 is not available as far as I can tell.
>
> It's actually a subkey, so if you updated Nicolas's key from the server it
> should verify correctly. I do agree that it's confusing, though.

So if I understand correctly, there isn't anything to fix here, and I'm
closing this bug report.  (If I'm mistaken, and there's something that
can be done to make this less confusing, please respond to the debbugs
address and we'll reopen.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-09-22 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 23:36 bug#35060: 26.1; Incorrect OpenPGP key on Emacs site Andrew Luke Nesbit
2019-03-31 15:09 ` Eli Zaretskii
2019-03-31 15:16   ` Andrew Luke Nesbit
2019-03-31 16:23     ` Alan Third
2019-04-02  6:13       ` Andrew Luke Nesbit
2019-04-02 13:59         ` Alan Third
2021-09-22 21:50           ` Lars Ingebrigtsen [this message]

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=87czp0qnys.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=35060@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=ullbeking@andrewnesbit.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 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).