unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Pierre-Henry Fröhring" <contact@phfrohring.com>, 53827@debbugs.gnu.org
Subject: [bug#53827] [PATCH] Add a TLDR entry to the cookbook for building Guix from Git.
Date: Sun, 06 Feb 2022 23:06:32 +0100	[thread overview]
Message-ID: <c89c9ce54ca883af6355964ebcf5807009db10c0.camel@telenet.be> (raw)
In-Reply-To: <20220206213344.3117861-1-contact@phfrohring.com>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

Pierre-Henry Fröhring schreef op zo 06-02-2022 om 22:33 [+0100]:
> +guix environment guix --pure --ad-hoc fd
> +./bootstrap
> +guix_db_prefix=$(fd -p '.*/guix/db$' /)
> +guix_db_prefix=$@{guix_db_prefix%/guix/db@}

What's this 'fd' and guix_db_prefix about?
If this is necessary, shouldn't it be documented in the main manual.

> +./configure --localstatedir="$guix_db_prefix"
> +exit
> +make authenticate

This "make authenticate" gives a false sense of security -- the MITM
attacker could have changed the Makefile.am to let the 'authenticate'
target be a no-op.  Likewise, authentication must happen before
./bootstrap and ./configure otherwise it's too late.

Also, didn't this authentication already happen in

> +@node Authentication
> +@section Authentication
> +
> +@example
> +git fetch origin keyring:keyring
> +guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad \
> +  "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA"

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-02-06 22:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06 21:33 [bug#53827] [PATCH] Add a TLDR entry to the cookbook for building Guix from Git Pierre-Henry Fröhring
2022-02-06 22:02 ` Maxime Devos
2022-02-15  9:20   ` Ludovic Courtès
2022-02-15 10:10     ` Pierre-Henry Fröhring
2022-02-16 13:36       ` Ludovic Courtès
2022-02-16 14:36         ` zimoun
2022-02-16 15:50         ` Pierre-Henry Fröhring
2022-02-16 16:16         ` Leo Famulari
2022-02-16 20:37           ` Pierre-Henry Fröhring
2022-02-17 10:38           ` Ludovic Courtès
2022-02-06 22:02 ` Maxime Devos
2022-02-06 22:03 ` Maxime Devos
2022-02-06 22:06 ` Maxime Devos [this message]
2022-02-06 22:07 ` Maxime Devos
2022-02-06 22:09 ` Maxime Devos
2022-02-06 23:10   ` Pierre-Henry Fröhring
2022-02-06 23:03 ` [bug#53827] [PATCH] Add a TLDR entry " Pierre-Henry Fröhring

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=c89c9ce54ca883af6355964ebcf5807009db10c0.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53827@debbugs.gnu.org \
    --cc=contact@phfrohring.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).