Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
Create a repository, rsync it to my homelab server, place into a
directory that is owned by a:a_and_b and has -R file mod of 770. Then
cloned that
into a new, bare repository with the same name, say on
/path/to/bare_repo. Then I prepared ssh auth via key on new machine, so
that user b can lo
g in to homelab without password. Then tried to clone the repository
with `git clone b@local-name:/path/to/bare_repo` and variations
prepending `s
sh://` and appending `/.git`. Got error
fatal: detected dubious ownership in repository at '/path/to/bare_repo'
To add an exception for this directory, call:
git config --global --add safe.directory /path/to/bare_repo
[The following is a rough translation, as the machine is in German and
so was this message]
fatal: could not read from remote repository
Please ensure that you have the correct access rights
and the repository exists
I then execute the command it suggests and confirm that the appropriate
line has been added to my git config
Retry - same error
Test if there is actually a problem with access rights by copying the
repository with `rsync -r b@local-name:/path/to/bare_repo ./`. No issue, eve
rything gets copied
What did you expect to happen? (Expected behavior)
Firstly, no issue at all, as cloning from a remote (bare) repository
that _isn't owned by me_ seems like standard usage of git. People are
bound t
o run into this in projects of more than one person, unless they use the
more elaborate implementations of vendors like github. My understanding w
ould be that this is how git should "naturally" work.
Then, the error being fixed after I apply the command it suggested.
What happened instead? (Actual behavior)
Unable to interact with repository unless I change ownership of the
remote to exactly the user that is used for cloning over ssh.
What's different between what you expected and what actually happened?
It cannot be made to work
Anything else you want to add:
This report is made from a different machine that runs a very similar OS
(NixOS 25.11).
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.47.2
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path:
/nix/store/gwgqdl0242ymlikq9s9s62gkp5cvyal3-bash-5.2p37/bin/bash
libcurl: 8.11.1
OpenSSL: OpenSSL 3.3.2 3 Sep 2024
zlib: 1.3.1
uname: Linux 6.6.32 #1-NixOS SMP PREEMPT_DYNAMIC Sat May 25 14:22:56 UTC
2024 x86_64
compiler info: gnuc: 13.3
libc info: glibc: 2.40
$SHELL (typically, interactive shell): /run/current-system/sw/bin/fish
[Enabled Hooks]
not run from a git repository - no hooks to show
