From: Ali Elshishini <shishini@outlook.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "55666@debbugs.gnu.org" <55666@debbugs.gnu.org>
Subject: bug#55666: enhancement request - SHA-256 for emacs downloads
Date: Fri, 27 May 2022 11:46:11 +0000 [thread overview]
Message-ID: <DM5PR19MB46804F23E0591C7B79C67363DBD89@DM5PR19MB4680.namprd19.prod.outlook.com> (raw)
In-Reply-To: <875ylr8cmq.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
A checksum file (a file containing all checksums) can be included in the ftp folders
(each folder can have one checksums file for the files it contains)
This way the web page won't have to be updated with every release
Otherwise if you absolutely can't, please add clear instructions on how to verify the downloads using the signatures, I personally tried my best and still failed
Thanks
Ali
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Lars Ingebrigtsen <larsi@gnus.org>
Sent: Friday, May 27, 2022 6:59:25 AM
To: Ali Elshishini <shishini@outlook.com>
Cc: 55666@debbugs.gnu.org <55666@debbugs.gnu.org>
Subject: Re: bug#55666: enhancement request - SHA-256 for emacs downloads
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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[-- Attachment #2: Type: text/html, Size: 2653 bytes --]
next prev parent reply other threads:[~2022-05-27 11:46 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR19MB46804F23E0591C7B79C67363DBD89@DM5PR19MB4680.namprd19.prod.outlook.com \
--to=shishini@outlook.com \
--cc=55666@debbugs.gnu.org \
--cc=larsi@gnus.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.