From: Ali Elshishini <shishini@outlook.com>
To: Corwin Brust <corwin@bru.st>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"55666@debbugs.gnu.org" <55666@debbugs.gnu.org>
Subject: bug#55666: enhancement request - SHA-256 for emacs downloads
Date: Sun, 29 May 2022 17:08:46 +0000 [thread overview]
Message-ID: <DM5PR19MB46801CE49BE2C8F4D1A427B0DBDA9@DM5PR19MB4680.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CAJf-WoRCRFzyibC7z2rx01R9DbXxUBp0WYSsyWg1_x9+Fg7q0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
First sorry for top posting, I am using hotmail/outlook, and dont know how to setup bottom posting
Also honestly, I never really knew about this convention of bottom posting
Second, that a lot Corwin, adding the SHA hashes will be great
Finally, just my 2 cent, SHA1 is to my knowledge is considered obsolete and broken https://en.wikipedia.org/wiki/SHA-1
So I think SHA-256 should be enough, and if you want to can consider SHA-512
Most project I see use SHA-256, and only very few offer or use SHA-512
Thanks
Ali
________________________________
From: Corwin Brust <corwin@bru.st>
Sent: May 29, 2022 3:42 AM
To: Ali Elshishini <shishini@outlook.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>; 55666@debbugs.gnu.org <55666@debbugs.gnu.org>
Subject: Re: bug#55666: enhancement request - SHA-256 for emacs downloads
On Fri, May 27, 2022 at 6:46 AM Ali Elshishini <shishini@outlook.com> wrote:
>
> 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)
I think this is a great idea. If nobody objects, I'll start including
something along these lines with my next upload of Windows binaries
(or maybe sooner, backfilling something for 28.1).
For the moment, you can get SHA1 sums for all (or at least, nearly
all) the binaries I've created from here:
https://corwin.bru.st/emacs-28/README
(The parent folder --which has indexing enabled-- is where I've been
staging my files before uploading to the GNU FTP servers and often
includes other builds that I don't plan to upload.)
If these don't work LMK and I'll regenerate the README file. I do
have a script for that but it will take a little fooling around to
make it worthly of including on the GNU FTP site (presuming others
agree with me your idea of adding files with SHA1 information to the
FTP folders is a good one).
Thanks for the suggestion.
BTW, you can also get my public key from Savannah by clicking "Download GPG
Key" from my profile page, here:
https://savannah.gnu.org/users/carlc
[-- Attachment #2: Type: text/html, Size: 4447 bytes --]
next prev parent reply other threads:[~2022-05-29 17:08 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 [this message]
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
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=DM5PR19MB46801CE49BE2C8F4D1A427B0DBDA9@DM5PR19MB4680.namprd19.prod.outlook.com \
--to=shishini@outlook.com \
--cc=55666@debbugs.gnu.org \
--cc=corwin@bru.st \
--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 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).