unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: bo0od <bo0od@riseup.net>, 47634@debbugs.gnu.org
Subject: bug#47634: Accompany .asc and .DIGESTS keys for the ISO
Date: Sun, 18 Apr 2021 12:40:10 +0200	[thread overview]
Message-ID: <875z0jlvud.fsf@gnu.org> (raw)
In-Reply-To: <87y2dqlvqj.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Sat, 10 Apr 2021 12:27:32 +1000")

Hi all,

Carlo Zancanaro <carlo@zancanaro.id.au> skribis:

> I'm not convinced there's much value to add anything beyond the
> signatures, and I think there is some cost. Having multiple 
> verification options makes the download page more confusing (by
> providing more choices to do the same thing), and may make it less 
> likely that people do any verification.

Agreed.

> I think there may be a larger conversation to have around using
> something like Signify rather than PGP/GPG, but I'm not familiar 
> enough with Signify to have an opinion about that at the moment.

Right.  OpenPGP isn’t great for software signing, but it’s widespread,
and that’s an important criterion if we are to allow users to
authenticate what they download.  Tools like Signify are certainly worth
looking at, but I see it as a longer-term option.

I’m closing this issue since it’s not really actionable.

Thanks,
Ludo’.




      parent reply	other threads:[~2021-04-18 10:41 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
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 [this message]

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=875z0jlvud.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47634@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    --cc=carlo@zancanaro.id.au \
    /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).