From: Josselin Poiret <dev@jpoiret.xyz>
To: wolf <wolf@wolfsden.cz>, Wojtek Kosior <koszko@koszko.org>
Cc: "Simon Tournier" <zimon.toutoune@gmail.com>,
"Nicolas Débonnaire" <n.debonnaire@gmail.com>,
guix-devel@gnu.org
Subject: Re: Building from git
Date: Sat, 09 Sep 2023 10:32:43 +0200 [thread overview]
Message-ID: <87a5tvvj9w.fsf@jpoiret.xyz> (raw)
In-Reply-To: <ZPsBdMVbbkN9tFUh@ws>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
Hi both of you (I'm replying to both at the same time),
wolf <wolf@wolfsden.cz> writes:
On 2023-09-08 11:47:56 +0200, Wojtek Kosior wrote:
> Hello Josselin
>
> > wolf <wolf@wolfsden.cz> writes:
> >
> > > Hmm, but the recipe for the authenticate rule comes from the (possibly)
> > > compromised source, no? So the attacker can just modify the recipe instead of
> > > the command going the authentication. Am I missing something?
> >
> > You can use a previously trusted guix to do the authentication. `make
> > authenticate` is here for committers to check that their commits are all
> > properly signed before pushing (it's used as a pre-push hook).
>
> From my understanding of the documentation, `make authenticate` is not
> just for committers but for all people who do a `git pull` in Guix tree
> and want to verify that the newly pulled commits do come from the
> committers. It it is not the case, then the documentation should
> probably be modified to make it clear.
>
> The recipe is not from an untrusted source mecause the Makefile is not
> tracked by git. Rather, it gets generated when first building Guix. And
> — as the documentation instructs — the initial checkout gets
> authenticated with `guix git authenticate` rather than with `make
> authenticate` so it can't get compromised that easily.
If you've already authenticated the initial check-out, what is the point
of `make authenticate` then? Maybe the manual isn't that clear, but as
wolf points out `make authenticate` itself cannot be a guarantee as it
requires trust in the Makefiles, creating a chicken-and-egg problem
.
> I mean, if make authenticate is just for the convenience of the committers, then
> this is completely fine. But the documentation does not currently read that
> way.
Yes, I believe this should then be clarified.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
prev parent reply other threads:[~2023-09-09 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 9:03 Building from git Nicolas Débonnaire
2023-09-05 14:18 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-09-07 12:06 ` Simon Tournier
2023-09-07 16:37 ` Bruno Victal
2023-09-07 17:45 ` wolf
2023-09-07 18:59 ` Simon Tournier
2023-10-23 17:16 ` Nicolas Débonnaire
2023-09-08 9:10 ` Josselin Poiret
2023-09-08 9:47 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-09-08 11:11 ` wolf
2023-09-09 8:32 ` Josselin Poiret [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=87a5tvvj9w.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=koszko@koszko.org \
--cc=n.debonnaire@gmail.com \
--cc=wolf@wolfsden.cz \
--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).