From: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
To: "Jonathan Frederickson" <jonathan@terracrypt.net>,
"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: Tue, 13 Aug 2024 18:23:29 +0200 [thread overview]
Message-ID: <PAXP251MB034801A990A1854F83599B5CF3862@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <3ad5baad-2ab6-4fa4-8788-717f827ccf86@app.fastmail.com>
"Jonathan Frederickson" <jonathan@terracrypt.net> writes:
> Guix accepting substitutes from servers without trusted signing keys if the same substitutes are available bit-for-bit on a trusted substitute server felt like it could be a hint at something. But your trusted build servers need to have built a package anyway for you to accept the same package from an untrusted one, so that doesn't avoid needing a lot of computing power in a trusted build farm.
Hello!
Wouldn't it be enough to have a few independent seeders that have the
same derivation output? We could have a field in the p2p service type
which allows the user to configure a "level of trust", where the user
specifies the minimum number of seeders with the same output for the
daemon to accept the substitute.
Regards,
Sergio.
next prev parent reply other threads:[~2024-08-13 16:24 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 [this message]
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
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=PAXP251MB034801A990A1854F83599B5CF3862@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM \
--to=sergio.pastorperez@outlook.es \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=jonathan@terracrypt.net \
--cc=ludo@gnu.org \
--cc=marek@marekpasnikowski.pl \
/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).