all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Maxime Devos" <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: U.S. Midwest based build farm
Date: Sat, 11 Jun 2022 20:13:30 +0000	[thread overview]
Message-ID: <19713f46b29fe34dd5c4f86d9634dec2@dismail.de> (raw)
In-Reply-To: <1c9065963fe7fed97613bc641e40d5f082c60e9b.camel@telenet.be>

June 11, 2022 4:00 PM, "Maxime Devos" <maximedevos@telenet.be> wrote:

> jbranso@dismail.de schreef op za 11-06-2022 om 16:06 [+0000]:
> 
>> What's good and/or bad about this idea?
> 
> A positive point: extra resources, could be useful for reproducibility
> testing, ...?

That's actually a good idea.  I could give limited ssh access to a few
guix developers.  Those guix developers could use my old and hopefully 
more powerful machines to quickly compile software.  Rust takes ages
to compile...

> 
> A negative point: extra points through with malware can be introduced
> (->compromises). Can be solved by reproducible builds and variation of
> "guix challenge". Unfortunately, "guix challenge" is inherently racy.
> "guix substitute" currently only checks that the narinfo has a _single_
> authorised signature, maybe it can be adjusted to allow the user to
> ask: ‘only consider a substitute to be authorised if the same hash is
> signed by N different authorised keys’?
> 

Thanks for the feedback.  We could also use the machines as a mirror
or an additional substitute server.  

> Other points: ...?
> 
> Greetings,
> Maxime.


      parent reply	other threads:[~2022-06-11 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 16:06 U.S. Midwest based build farm jbranso
2022-06-11 20:00 ` Maxime Devos
2022-06-11 23:05   ` Vagrant Cascadian
2022-06-11 20:13 ` jbranso [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19713f46b29fe34dd5c4f86d9634dec2@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.