From: "Nicolas Débonnaire" <n.debonnaire@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: wolf <wolf@wolfsden.cz>, guix-devel@gnu.org
Subject: Re: Building from git
Date: Mon, 23 Oct 2023 19:16:59 +0200 [thread overview]
Message-ID: <CANOKM3f1+-3WC0G9Ri497rLE+4CZKySnr4mtj+akXNtLAP7y7Q@mail.gmail.com> (raw)
In-Reply-To: <86v8clajxs.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]
Hi,
Looks like it's working.
I was able to complete the "building from git" section of the documentation
after an update of guix.
Thanks everyone.
Le sam. 9 sept. 2023 à 11:01, Simon Tournier <zimon.toutoune@gmail.com> a
écrit :
> Hi,
>
> On Thu, 07 Sep 2023 at 19:45, wolf <wolf@wolfsden.cz> wrote:
>
> >> The Makefile does not run ‘guix git authenticate’ using ./pre-inst-env.
> >> And that’s probably to ensure the source of trust. If one corrupt the
> >> commit that is built, then ’make authenticate’ would authenticate the
> >> corruption because it would run the corrupted newly built guix command.
> >> Currently, ’make authenticate’ run one guix command that had already
> >> been authenticated. Well, that’s my understanding.
> >
> > 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?
>
> Yes, the corruption of Makefile.am can be the corruption I was talking
> about.
>
> Well, for more explanations one can maybe read:
>
> [bug#57909] bug#57910: [PATCH] Add link to 'pre-inst-env' from
> 'installing from git' docs
> Ludovic Courtès <ludo@gnu.org>
> Sat, 24 Sep 2022 17:58:29 +0200
> id:87k05s7oii.fsf_-_@gnu.org
> https://issues.guix.gnu.org//57910
> https://issues.guix.gnu.org/msgid/87k05s7oii.fsf_-_@gnu.org
> https://yhetil.org/guix/87k05s7oii.fsf_-_@gnu.org
>
> [bug#57909] bug#57910: [PATCH] Add link to 'pre-inst-env' from
> 'installing from git' docs
> Maxime Devos <maximedevos@telenet.be>
> Sat, 24 Sep 2022 18:23:10 +0200
> id:ec49e6c2-a542-7d95-0d73-10b2816c59d2@telenet.be
> https://issues.guix.gnu.org//57910
>
> https://issues.guix.gnu.org/msgid/ec49e6c2-a542-7d95-0d73-10b2816c59d2@telenet.be
>
> https://yhetil.org/guix/ec49e6c2-a542-7d95-0d73-10b2816c59d2@telenet.be
>
> Cheers,
> simon
>
[-- Attachment #2: Type: text/html, Size: 3582 bytes --]
next prev parent reply other threads:[~2023-10-23 17:17 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 [this message]
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
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=CANOKM3f1+-3WC0G9Ri497rLE+4CZKySnr4mtj+akXNtLAP7y7Q@mail.gmail.com \
--to=n.debonnaire@gmail.com \
--cc=guix-devel@gnu.org \
--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).