From: Eli Zaretskii <eliz@gnu.org>
To: Ali Elshishini <shishini@outlook.com>
Cc: larsi@gnus.org, corwin@bru.st, 55666@debbugs.gnu.org
Subject: bug#55666: enhancement request - SHA-256 for emacs downloads
Date: Sat, 28 May 2022 22:27:18 +0300 [thread overview]
Message-ID: <83ee0dlap5.fsf@gnu.org> (raw)
In-Reply-To: <DM5PR19MB4680165E6782DC281125C887DBDB9@DM5PR19MB4680.namprd19.prod.outlook.com> (message from Ali Elshishini on Sat, 28 May 2022 19:17:49 +0000)
> From: Ali Elshishini <shishini@outlook.com>
> CC: "corwin@bru.st" <corwin@bru.st>, "larsi@gnus.org" <larsi@gnus.org>,
> "55666@debbugs.gnu.org" <55666@debbugs.gnu.org>
> Date: Sat, 28 May 2022 19:17:49 +0000
>
> But again, verifying the signature on windows doesn't seem to instill confidence at all
> Corvwin doesnt have a certified key
> I am not a certificate expert, so I dont know how all of this works
>
> So, I still hope Corwin or the Windows Binaries volunteers will still be able to provide
> SHA-256 hashes
Hey, I just answered a question you asked, that's all. I assumed that
if you are asking it, it is important for you to know the answer.
next prev parent reply other threads:[~2022-05-28 19:27 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
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 [this message]
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=83ee0dlap5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55666@debbugs.gnu.org \
--cc=corwin@bru.st \
--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).