From: Colin Stagner <ask@howdoi.land>
To: Mike Lodispoto <mike@lodispoto.com>, git@vger.kernel.org
Subject: Re: Shared bare repository dubious ownership error after 2.40.1-r0
Date: Wed, 17 Jul 2024 23:24:34 -0500 [thread overview]
Message-ID: <984140ad-b2b9-4336-84db-552428071f7e@howdoi.land> (raw)
In-Reply-To: <dd703bdc-f485-4162-92a5-fd2828b69604@lodispoto.com>
Mike,
On 7/10/24 18:16, Mike Lodispoto wrote:
> | $ git pull
> | fatal: detected dubious ownership in repository at
This appears to be known behavior introduced as a fix for
CVE-2024-32004. It appears that the safe.directory restrictions now
apply to fetch and clone as well. See the release notes for v2.45.1 [1].
You can fix this by adding the path containing your repositories to the
safe.directory configuration parameter as Git recommends. Whether or not
you should is another matter—this can expose your devs to attacks from
other user accounts.
I also have small workgroups that use NFS and other network filesystems
to share repositories. Are there any plans to make cloning a local
repository safe?
Colin
References
[1]: <https://lore.kernel.org/git/xmqqv83g4937.fsf@gitster.g/>
next prev parent reply other threads:[~2024-07-18 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:16 Shared bare repository dubious ownership error after 2.40.1-r0 Mike Lodispoto
2024-07-18 4:24 ` Colin Stagner [this message]
2024-07-18 15:00 ` Ben Zanin
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=984140ad-b2b9-4336-84db-552428071f7e@howdoi.land \
--to=ask@howdoi.land \
--cc=git@vger.kernel.org \
--cc=mike@lodispoto.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.
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).