From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Philip McGrath" <philip@philipmcgrath.com>
Cc: 47614-done@debbugs.gnu.org
Subject: bug#47614: [security] Chunked store references in .zo files in Racket 8
Date: Sat, 17 Apr 2021 05:25:47 -0400 [thread overview]
Message-ID: <87h7k58dop.fsf@netris.org> (raw)
In-Reply-To: <87blae44gx.fsf_-_@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> IIUC, now that <https://issues.guix.gnu.org/47180> has been closed,
> this bug is fixed. Am I right?
Yes, I believe so. All store items referenced by Racket now seem to be
properly grafted, so I'm closing this bug now.
The more general issue with the grafting code--namely that since commit
57bdd79e48, it no longer has the desirable property of checking every
byte against an expected value before rewriting it, which can lead to
silent corruption of files such as Racket .zo files if any store items
references sneak in--can be addressed in another bug report.
Thanks,
Mark
next prev parent reply other threads:[~2021-04-17 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 1:20 Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614) Jack Hill
2021-04-07 1:38 ` Philip McGrath
2021-04-07 1:48 ` bug#47614: [security] Chunked store references in .zo files in Racket 8 #47614 Philip McGrath
2021-04-16 15:46 ` bug#47614: [security] Chunked store references in .zo files in Racket 8 Ludovic Courtès
2021-04-16 19:46 ` Philip McGrath
2021-04-17 9:25 ` Mark H Weaver [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 11:06 Mark H Weaver
2021-04-06 17:39 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-06 21:27 ` Mark H Weaver
2021-04-06 22:18 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-13 21:27 ` Mark H Weaver
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=87h7k58dop.fsf@netris.org \
--to=mhw@netris.org \
--cc=47614-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=philip@philipmcgrath.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 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.