From: Julien Moutinho <julm+public-inbox@sourcephile.fr>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Test failures due to core.sharedRepository and sandboxing
Date: Tue, 25 Oct 2022 18:49:38 +0200 [thread overview]
Message-ID: <20221025164938.agffzitrsgn4pbcu@sourcephile.fr> (raw)
In-Reply-To: <20221025101756.M341966@dcvr>
Le mar. 25 oct. 2022 10h17 +0000, Eric Wong a écrit :
> My brain is very tired atm, but I'm wondering if git should
> strip S_ISGID and retry if it hits EPERM...
I've asked on git@ here
https://public-inbox.org/git/20221025163024.uutqv7w24yi4eo5i@sourcephile.fr/T/#u
> On a traditional Unix-like system, the objective of 0600 is to
> ensure only the user running lei can read their own email.
> AFAIK, that's standard behavior for MUAs creating local files
> (I only know it's mutt behavior off the top-of-my-head).
>
> That said, I don't know how NixOS's sandbox is different than a
> traditional system.
nix's build sandbox denies g+s, but that sandbox only applies
when building a package (which includes running its tests).
Once the package is built, that sandbox is no longer used,
leaving the package free to use g+s when run by users.
> Is setting any value of core.sharedRepository even worthwhile on NixOS?
AFAIK NixOS would be like any other Linux-based OS on that matter.
Cheers,
prev parent reply other threads:[~2022-10-25 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 21:58 Test failures due to core.sharedRepository and Julien Moutinho
2022-10-25 10:17 ` Eric Wong
2022-10-25 16:49 ` Julien Moutinho [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221025164938.agffzitrsgn4pbcu@sourcephile.fr \
--to=julm+public-inbox@sourcephile.fr \
--cc=e@80x24.org \
--cc=meta@public-inbox.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 public inbox
https://80x24.org/public-inbox.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).