From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Reproducible Builds Summit 2022
Date: Sat, 05 Nov 2022 14:25:38 +0100 [thread overview]
Message-ID: <87mt95h6n3.fsf@cbaines.net> (raw)
In-Reply-To: <86zgd5vb0m.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> Really cool! Thank you for the heads-up.
>
> On Thu, 03 Nov 2022 at 15:44, Efraim Flashner <efraim@flashner.co.il> wrote:
>
>> We should also continue working on implementing a
>> change in the ACL to allow requiring a K of N agreement between
>> different substitute servers that a build is correct^2.
>
> I am not a specialist about consensus algorithm so maybe I am totally
> out of topic. This K-of-N agreement looks like a Proof of Stake [1].
I think it's useful to keep this simple.
Going back to [1], currently we only support users trusting substitutes
if they're signed by any key they trust.
I'd like to see support for more complex policies, like only trusting
substitutes if there's a valid signature from two substitute servers
(two different keys). So trusting substitutes that have been built by
two substitute servers, and they've come to the same result.
1: https://lists.gnu.org/archive/html/guix-devel/2020-06/msg00179.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2022-11-05 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:44 Reproducible Builds Summit 2022 Efraim Flashner
2022-11-03 15:25 ` Ludovic Courtès
2022-11-05 10:18 ` Reproducible Builds Summit 2022, nar support in diffoscope Christopher Baines
2022-11-05 18:04 ` Ludovic Courtès
2022-11-05 12:30 ` Reproducible Builds Summit 2022 zimoun
2022-11-05 13:25 ` Christopher Baines [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=87mt95h6n3.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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/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).