all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Larry Doolittle <larry@doolittle.boa.org>
To: General discussions about reproducible builds
	<rb-general@lists.reproducible-builds.org>
Cc: Jan Nieuwenhuizen <janneke@gnu.org>,
	guix-devel@gnu.org, bootstrappable@freelists.org
Subject: Re: GNU Mes 0.24 released
Date: Sat, 7 May 2022 16:11:06 -0700	[thread overview]
Message-ID: <Ynb8imBbn0iBWyjE@doolittle.boa.org> (raw)
In-Reply-To: <87k0axynso.fsf@gnu.org>

Ludovic and friends -

On Sun, May 08, 2022 at 12:34:47AM +0200, Ludovic Courtès wrote:
> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> > Mes has now been ported to M2-Planet and can be bootstrapped using
> > stage0-posix[0], starting from the 357-byte hex0 binary of the
> > bootstrap-seeds[1], as was promised at FOSDEM'21[2].
> This is amazing… congrats to you & everyone involved!  You made it!  :-)

+1

> The common objection is: “you’re building from source but you’re not
> gonna audit all that source code anyway, so why bother?”  [...]
> Supply chain security is a spectrum and I think this achievement changes
> what we can expect and demand.

I've had this conversation before, any my analogy is to the
three legs of a stool.  Bootstrapped toolchains, reproducible builds,
and source-code audits.  Each one is arguably useless without the others,
but taken together, you've actually accomplished something meaningful.
Maybe I should also include "cryptographically signed artifact distribution"
on that list.

 - Larry


  reply	other threads:[~2022-05-08 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 18:04 GNU Mes 0.24 released Jan Nieuwenhuizen
2022-05-07 22:34 ` Ludovic Courtès
2022-05-07 23:11   ` Larry Doolittle [this message]
2022-05-08 13:55     ` Sébastien Lerique
2022-05-08 19:49       ` Larry Doolittle
2022-05-09 14:00     ` indieterminacy
2022-05-09  0:03   ` Thiago Jung Bauermann
2022-05-09 20:22     ` Orians, Jeremiah (DTMB)

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=Ynb8imBbn0iBWyjE@doolittle.boa.org \
    --to=larry@doolittle.boa.org \
    --cc=bootstrappable@freelists.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.org \
    --cc=rb-general@lists.reproducible-builds.org \
    /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.