From: "Sébastien Lerique" <sl@eauchat.org>
To: Larry Doolittle <larry@doolittle.boa.org>
Cc: General discussions about reproducible builds
<rb-general@lists.reproducible-builds.org>,
Jan Nieuwenhuizen <janneke@gnu.org>,
bootstrappable@freelists.org, guix-devel@gnu.org
Subject: Re: GNU Mes 0.24 released
Date: Sun, 08 May 2022 22:55:41 +0900 [thread overview]
Message-ID: <87mtfsjdty.fsf@eauchat.org> (raw)
In-Reply-To: <Ynb8imBbn0iBWyjE@doolittle.boa.org>
Amazing indeed!
On 07 May 2022 at 16:11, Larry Doolittle <larry@doolittle.boa.org> wrote:
>> 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.
>
In a similar line, Bunnie Huang gave an interesting talk about the
hardware trust level a few years ago [0], which led to the Precursor
project [1,2].
Cheers,
Sébastien
[0] https://media.ccc.de/v/36c3-10690-open_source_is_insufficient_to_solve_trust_problems_in_hardware
[1] https://www.crowdsupply.com/sutajio-kosagi/precursor
[2] https://www.bunniestudios.com/blog/?p=5979
next prev parent reply other threads:[~2022-05-08 15:01 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
2022-05-08 13:55 ` Sébastien Lerique [this message]
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=87mtfsjdty.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=bootstrappable@freelists.org \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=larry@doolittle.boa.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.