From: Maxime Devos <maximedevos@telenet.be>
To: 47584@debbugs.gnu.org
Subject: bug#47584: [DRAFT PATCH v2 0/4] Fix race condition in mkdir-p/perms
Date: Fri, 28 Oct 2022 18:03:26 +0200 [thread overview]
Message-ID: <0d5b596b-cc47-aafc-bee9-5b23d734298c@telenet.be> (raw)
In-Reply-To: <1a6ed722dfdd96dc8d53f939aa8e440ca7c29213.camel@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 226 bytes --]
> TODO: change the Guile used for activation to some
> commit that has openat etc, [...]
This is done now, but "make check-system" now fails due to an openssl
build failure, see latest patch, so not yet appliable ...
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-28 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 16:09 bug#47584: Race condition in ‘copy-account-skeletons’: possible privilege escalation Maxime Devos
2021-04-03 16:22 ` Maxime Devos
2021-04-03 16:32 ` Maxime Devos
2021-04-03 20:15 ` Ludovic Courtès
2021-04-03 16:26 ` Maxime Devos
2021-04-03 20:45 ` Ludovic Courtès
2021-04-03 20:49 ` Ludovic Courtès
2021-04-04 13:29 ` Maxime Devos
2021-04-03 20:27 ` Ludovic Courtès
2021-04-03 20:33 ` Ludovic Courtès
2021-04-04 7:36 ` Maxime Devos
2021-04-05 19:54 ` Ludovic Courtès
2021-04-06 9:56 ` Maxime Devos
2021-04-06 11:57 ` Ludovic Courtès
2021-04-07 18:28 ` Maxime Devos
2022-10-21 9:31 ` Maxime Devos
2022-10-28 16:03 ` Maxime Devos [this message]
2022-10-28 16:04 ` bug#47584: [PATCH 1/3] guile-next: Update to 3.0.8-793fb46 Maxime Devos
2022-10-28 16:04 ` bug#47584: [PATCH 2/3] WIP gnu: Change the Guile used for activation to one that has 'openat' Maxime Devos
2022-10-28 16:04 ` bug#47584: [PATCH 3/3] activation: Fix TOCTTOU in mkdir-p/perms Maxime Devos
2022-10-28 16:05 ` bug#47584: [PATCH 1/3] guile-next: Update to 3.0.8-793fb46 Maxime Devos
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=0d5b596b-cc47-aafc-bee9-5b23d734298c@telenet.be \
--to=maximedevos@telenet.be \
--cc=47584@debbugs.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.