unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org,  rb-general@lists.reproducible-builds.org,
	bootstrappable@freelists.org
Subject: Re: GNU Mes 0.24 released
Date: Sun, 08 May 2022 00:34:47 +0200	[thread overview]
Message-ID: <87k0axynso.fsf@gnu.org> (raw)
In-Reply-To: <87fslr4xqd.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 02 May 2022 20:04:42 +0200")

Heya,

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!  :-)

The ability to build literally everything from source, with reproducible
builds, is a game changer IMO when it comes to supply chain security.

The common objection is: “you’re building from source but you’re not
gonna audit all that source code anyway, so why bother?”  I think it’s
akin to security by obscurity.  That we collectively can and do fiddle
with all this code makes a practical difference; that this is all
transparent means that backdoors become harder to hide.

Supply chain security is a spectrum and I think this achievement changes
what we can expect and demand.

Ludo’.


  reply	other threads:[~2022-05-07 22:35 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 [this message]
2022-05-07 23:11   ` Larry Doolittle
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

  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=87k0axynso.fsf@gnu.org \
    --to=ludo@gnu.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 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).