From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: 47634@debbugs.gnu.org, bo0od@riseup.net, leo@famulari.name
Subject: bug#47634: Accompany .asc and .DIGESTS keys for the ISO
Date: Fri, 09 Apr 2021 08:57:00 +1000 [thread overview]
Message-ID: <8624B91E-1A4F-4455-880A-E5664C27D5B1@zancanaro.id.au> (raw)
In-Reply-To: <d6171b07-515f-58e2-2cff-e6dbd721656b@riseup.net>
On 9 April 2021 3:34:20 am AEST, bo0od <bo0od@riseup.net> wrote:
>This is nicely written by Qubes documentation:
>
>https://www.qubes-os.org/security/verifying-signatures/
From that page:
> If you’ve already verified the signatures on the ISO directly, then verifying digests is not necessary.
Which implies that the signatures are sufficient, right?
What is the benefit to providing the key (.asc) and hashes (.DIGESTS)? The page you linked provides rationale for providing and checking digital signatures, but we already provide them.
Carlo
next prev parent reply other threads:[~2021-04-08 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 5:42 bug#47634: Accompany .asc and .DIGESTS keys for the ISO bo0od
2021-04-08 17:03 ` Leo Famulari
2021-04-08 17:34 ` bo0od
2021-04-08 22:57 ` Carlo Zancanaro [this message]
2021-04-09 22:17 ` bo0od
2021-04-10 2:27 ` Carlo Zancanaro
2021-04-10 21:24 ` bo0od
2021-04-18 10:40 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8624B91E-1A4F-4455-880A-E5664C27D5B1@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=47634@debbugs.gnu.org \
--cc=bo0od@riseup.net \
--cc=leo@famulari.name \
/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/guix.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).