From: "Jonathan Frederickson" <jonathan@terracrypt.net>
To: "Felix Lechner" <felix.lechner@lease-up.com>,
"Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
"Marek Paśnikowski" <marek@marekpasnikowski.pl>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Re: Sustainable funding and maintenance for our infrastructure
Date: Sat, 24 Aug 2024 19:15:26 -0400 [thread overview]
Message-ID: <b82e2256-ecb4-422a-9520-c5a1ecf496cc@app.fastmail.com> (raw)
In-Reply-To: <87o75vb5p9.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
On Wed, Aug 14, 2024, at 9:21 AM, Felix Lechner wrote:
> The serving someone else's substitutes could also arise more innocently,
> for example via a technical misconfiguration or because of an incentive
> system that rewards the contribution of substitutes.
Yes, indeed. And you may very well want such an incentive system, because having many people distribute substitutes in a P2P system is a natural way for people to contribute their own bandwidth.
> Is it possible for someone to reliably attest that they individually
> built a reproducible work product? I believe the needed variation in
> inputs, like a hash, is incompatible with the goal of reproducability.
I think it's possible if the signature is detached from the reproducible work product to be signed. For example, it's like the difference between an embedded and detached signature of a file signed by GPG. Distributing a detached signature alongside a file doesn't change the hash of the file that's been signed.
Of course, you may not have built the build inputs yourself either - but those can be authenticated separately. (Recursion!)
[-- Attachment #2: Type: text/html, Size: 1545 bytes --]
next prev parent reply other threads:[~2024-08-24 23:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:24 Sustainable funding and maintenance for our infrastructure Ludovic Courtès
2024-07-03 1:13 ` indieterminacy
2024-07-04 16:37 ` Simon Tournier
2024-07-08 12:02 ` Ricardo Wurmus
2024-07-09 14:49 ` Simon Tournier
2024-07-11 9:23 ` Ludovic Courtès
2024-07-08 15:46 ` Vagrant Cascadian
2024-07-08 18:28 ` Vincent Legoll
2024-07-09 9:47 ` Tomas Volf
2024-07-11 10:33 ` Andreas Enge
2024-07-11 20:44 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-11 9:38 ` Ludovic Courtès
2024-07-12 10:44 ` Simon Tournier
2024-07-21 12:52 ` Ludovic Courtès
2024-07-08 16:27 ` Efraim Flashner
2024-07-08 17:21 ` Enrico Schwass
2024-07-11 10:48 ` Andreas Enge
2024-07-11 9:28 ` Ludovic Courtès
2024-08-01 22:11 ` Marek Paśnikowski
2024-08-13 2:53 ` Jonathan Frederickson
2024-08-13 16:23 ` Sergio Pastor Pérez
2024-08-13 23:38 ` Jonathan Frederickson
2024-08-14 13:21 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-08-24 23:15 ` Jonathan Frederickson [this message]
2024-08-21 22:07 ` P2P Guix package building and distribution Christine Lemmer-Webber
2024-08-22 9:05 ` Andreas Enge
2024-08-22 21:57 ` Samuel Christie via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2024-07-02 14:26 Sustainable funding and maintenance for our infrastructure 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=b82e2256-ecb4-422a-9520-c5a1ecf496cc@app.fastmail.com \
--to=jonathan@terracrypt.net \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=ludo@gnu.org \
--cc=marek@marekpasnikowski.pl \
--cc=sergio.pastorperez@outlook.es \
/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).