From: Michael Orlitzky <michael@orlitzky.com>
To: git@vger.kernel.org
Subject: safe.directory warnings for root-owned repositories
Date: Thu, 31 Oct 2024 00:23:04 -0400 [thread overview]
Message-ID: <ZyMGKHTnZDQ5JVuo@mertle> (raw)
If I create a new repository as root,
$ sudo git init
Initialized empty Git repository in /home/mjo/tmp/.git/
$ ls -alh
total 12K
drwxr-xr-x 3 mjo mjo 4.0K 2024-10-31 00:09 .
drwxr-x--- 17 mjo mjo 4.0K 2024-10-31 00:07 ..
drwxr-xr-x 6 root root 4.0K 2024-10-31 00:09 .git
and attempt to do anything in it, I get a safe.directory warning:
$ git status
fatal: detected dubious ownership in repository at '/home/mjo/tmp'
...
Does that make sense? In terms of ownership, root:root is as safe as
it gets.
I'm aware that safe.directory is only scratching the surface of these
"doing things in a directory that someone else can write to" exploits,
but within the limited scope of this one feature, root ownership does
not strike me as particularly dubious.
next reply other threads:[~2024-10-31 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 4:23 Michael Orlitzky [this message]
2024-10-31 5:38 ` safe.directory warnings for root-owned repositories Caleb White
2024-10-31 12:15 ` Michael Orlitzky
2024-10-31 20:04 ` Taylor Blau
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=ZyMGKHTnZDQ5JVuo@mertle \
--to=michael@orlitzky.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).