From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Christopher Baines <mail@cbaines.net>, help-guix@gnu.org
Subject: Re: Guix and remote trust
Date: Fri, 13 Dec 2019 09:48:34 +0100 [thread overview]
Message-ID: <87h824d319.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87h825wkj6.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> This sounds like guix gc --verify=contents. Debian has a similar feature
> I think, with dpkg --verify.
From the manual:
--8<---------------cut here---------------start------------->8---
When passing ‘--verify=contents’, the daemon computes the content
hash of each store item and compares it against its hash in the
database. Hash mismatches are reported as data corruptions.
Because it traverses _all the files in the store_, this command can
take a long time, especially on systems with a slow disk drive.
--8<---------------cut here---------------end--------------->8---
Is this still relevant remotely? If an untrusted third-party has root
access to the system, they can probably tamper with both the database
and the store, right?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-13 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:23 Guix and remote trust Pierre Neidhardt
2019-12-12 16:55 ` Christopher Baines
2019-12-13 8:48 ` Pierre Neidhardt [this message]
2019-12-13 11:05 ` zimoun
2019-12-13 12:24 ` Pierre Neidhardt
2019-12-13 12:50 ` zimoun
2019-12-13 13:05 ` Josh Marshall
2019-12-13 13:22 ` Pierre Neidhardt
2019-12-13 13:18 ` Pierre Neidhardt
2019-12-13 13:38 ` Pierre Neidhardt
2019-12-13 15:26 ` zimoun
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=87h824d319.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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.
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).