unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55666@debbugs.gnu.org, shishini@outlook.com
Subject: bug#55666: enhancement request - SHA-256 for emacs downloads
Date: Fri, 27 May 2022 15:28:32 +0300	[thread overview]
Message-ID: <835ylrnor3.fsf@gnu.org> (raw)
In-Reply-To: <875ylr8cmq.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  27 May 2022 12:59:25 +0200)

> Cc: 55666@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 27 May 2022 12:59:25 +0200
> 
> Ali Elshishini <shishini@outlook.com> writes:
> 
> > May you please include a list of SHA-256 hashes for the downloads in 
> > https://www.gnu.org/software/emacs/download.html
> >
> > This will provide an easy and secure way to verify downloads
> > Please note that the experience to verify the signature on windows is very poor
> > and it for me at least ended up with the file nor being verified because of missing
> > public key 
> >
> > A SHA-256 hash will be a simple solution
> 
> That would require people to edit that web page every time they generate
> a package, which would be error prone and require too much work of the
> people who build the packages.
> 
> The packages are signed, which I think should be more than sufficient,
> so I'm closing this bug report.

In addition, one can find the SHA values in the announcements made on
info-gnu-emacs.  Here's the one about Emacs 28.1:

  https://lists.gnu.org/archive/html/info-gnu-emacs/2022-04/msg00000.html

You can similarly search for announcements of the older releases.





  parent reply	other threads:[~2022-05-27 12:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 17:47 bug#55666: enhancement request - SHA-256 for emacs downloads Ali Elshishini
2022-05-27 10:59 ` Lars Ingebrigtsen
2022-05-27 11:46   ` Ali Elshishini
2022-05-29  7:42     ` Corwin Brust
2022-05-29 17:08       ` Ali Elshishini
2022-05-29 18:53         ` Corwin Brust
2022-05-29 19:46           ` Ali Elshishini
2022-05-27 12:28   ` Eli Zaretskii [this message]
2022-05-28  0:43     ` Ali Elshishini
2022-05-28  6:15       ` Eli Zaretskii
2022-05-28 17:14         ` Ali Elshishini
2022-05-28 19:06           ` Eli Zaretskii
2022-05-28 19:17             ` Ali Elshishini
2022-05-28 19:27               ` Eli Zaretskii
2022-05-28 20:31                 ` Ali Elshishini
2022-05-28 22:09                   ` Corwin Brust

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=835ylrnor3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55666@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=shishini@outlook.com \
    /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).