From: "Ludovic Courtès" <ludo@gnu.org>
To: ngraves@ngraves.fr
Cc: 74711@debbugs.gnu.org
Subject: bug#74711: Is grub broken and breaking Guix ?
Date: Tue, 10 Dec 2024 23:27:24 +0100 [thread overview]
Message-ID: <871pyfi377.fsf_-_@gnu.org> (raw)
In-Reply-To: <305651c5d363f13f253b8290e09ba497@ngraves.fr> (ngraves@ngraves.fr's message of "Sat, 07 Dec 2024 10:53:40 +0100")
ngraves@ngraves.fr skribis:
> By the way, guix install did work perfectly fine despite SSL
> certificates failing, does that mean that it doesn't do any SSL
> certificate verification ? Is that considered safe? How about
> man-in-the-middle and data-tampering attacks? Are they impossible due
> to sha checksums in Guix, or is that a vulnerability ?
The error with ‘guix pull’ comes from libgit2 when talking to
https://git.sv.gnu.org.
‘guix install’ does not do that. When it downloads substitutes, it
authenticates them (narinfos are signed) and checks their integrity once
the download is complete.
X.509 certificates do not matter at all here and are explicitly ignored;
see #:verify-certificate? in (guix scripts substitutes).
Ludo’.
next prev parent reply other threads:[~2024-12-10 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:47 bug#74711: Is grub broken and breaking Guix ? ngraves
2024-12-07 9:45 ` bug#74711: Sharing some progress ngraves
2024-12-07 9:53 ` ngraves
2024-12-10 22:27 ` Ludovic Courtès [this message]
2024-12-10 22:23 ` bug#74711: Certificate issues with ‘guix pull’ when system clock is in the past Ludovic Courtès
2024-12-10 23:38 ` bug#74711: Is grub broken and breaking Guix ? Ludovic Courtès
2024-12-10 23:17 ` Ludovic Courtès
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=871pyfi377.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=74711@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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).