all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: guix-devel@gnu.org
Subject: Re: Reproducible Containers Paper
Date: Tue, 17 Jan 2023 16:53:16 +0100	[thread overview]
Message-ID: <87a62hf98z.fsf@gnu.org> (raw)
In-Reply-To: <2D2CE548-0FF4-4D2B-A466-328D99835B4F@carldong.me> (Carl Dong's message of "Sun, 8 Jan 2023 17:56:30 -0800")

Hi Carl,

Carl Dong <contact@carldong.me> skribis:

> The paper is titled "Reproducible Containers”: https://dl.acm.org/doi/pdf/10.1145/3373376.3378519, featured by Meta in their post: https://developers.facebook.com/blog/post/2022/11/22/hermit-deterministic-linux-testing/

Interesting!  Probably a sledgehammer for reproducible builds… except
perhaps for timestamp issues, as you write.

> I was thinking about this in terms of how to have timestamp reproducibility inside Guix build containers which has been a problem in the past for building from source, their approach in 5.3 is interesting (but perhaps a bit invasive).

Yes, this bit is interesting:

  To ensure airtight interception of vDSO calls, DetTrace instead, just
  after each execve system call, replaces the vDSO library code with our
  implementation where each vDSO function makes a direct system
  call—which is duly intercepted via ptrace. We furthermore make the
  vvar page unreadable to prohibit any access to the raw
  nondeterministic data that vDSO timing calls use.

I wonder what this entails exactly, and whether one needs to ptrace
every single process to intercept exec calls in child processes, which
would be prohibitive.

Thanks for sharing!

Ludo’.


      reply	other threads:[~2023-01-17 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  1:56 Reproducible Containers Paper Carl Dong
2023-01-17 15:53 ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a62hf98z.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=contact@carldong.me \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.