Access issue after installing TortoiseGit

[John Emmas (johne53)]

I just downloaded 64-bit TortoiseGit 2.18.0.1 (for Windows) after previously using a much older version. Some of my pre-existing repos work fine but two of them give me the attached message when I try to use Show Log :-

It seems to be suggesting that these particular repo paths aren't owned by me. But they worked fine with my previous TortoiseGit. Any suggestions for how I can fix this?

[John Emmas (johne53)]

I should add a couple things which might be worth considering:-

1. I did try that git config command but it didn't help
2. All my git repo's are on a FAT32 drive - and AFAIK, FAT32 doesn't have the concept of ownership

[Sven Strickroth]

Hi,

the reason is a security feature of Git (added in 2022,
https://github.blog/2022-04-12-git-security-vulnerability-announced/#cve-2022-24765)
that checks whether the owner of a directory matches.

As you mentioned, you are using FAT32m you need to define an exception:
<https://weblog.west-wind.com/posts/2023/Jan/05/Fix-that-damn-Git-Unsafe-Repository>

If you know what you are doing and are the only user on your machine,
you can also disable the security check by using "*" as safe.directory.

Lastly, you also mentioned that you are using Msys2 Git, then you have
to enable the Msys2 hack to make TortoiseGit use the same config as
Msys2 Git (do NOT enable that setting for Git for Windows). Use
TortoiseGit settings -> advances settings to enable the hack and then
check TortoiseGit settings -> Git -> "View effective config" and make
sure it matches your Msys2 config. All information can be found here:
<https://tortoisegit.org/docs/tortoisegit/tgit-dug-settings.html>

Best,
Sven

Am 26.02.2026 um 16:53 schrieb John Emmas (johne53):
> I should add a couple things which might be worth considering:-
>

> 1. I did try that *git config *command but it didn't help
> 2. All my git repo's are on a FAT32 drive - and AFAIK, FAT32 doesn't

> have the concept of ownership
>
> On Thursday, February 26, 2026 at 11:26:01 AM UTC John Emmas (johne53)
> wrote:
>
> I just downloaded 64-bit TortoiseGit 2.18.0.1 (for Windows) after
> previously using a much older version. Some of my pre-existing repos
> work fine but two of them give me the attached message when I try to

> use *Show Log* :-

>
> It seems to be suggesting that these particular repo paths aren't
> owned by me. But they worked fine with my previous TortoiseGit. Any
> suggestions for how I can fix this?
>

> Capture-13.png
>
> --
> You received this message because you are subscribed to the Google
> Groups "tortoisegit-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to tortoisegit-us...@googlegroups.com
> <mailto:tortoisegit-us...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> tortoisegit-users/58b9cc12-f066-4243-
> a1f2-97945a36f20dn%40googlegroups.com <https://groups.google.com/d/
> msgid/tortoisegit-users/58b9cc12-f066-4243-
> a1f2-97945a36f20dn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[John Emmas (johne53)]

Many thanks Sven. I realised that the reason 'git config (etc)' hasn't been working was because it's read-only so I've fixed that and it's writable now.

Regarding git itself it was definitely Msys2 in the past but I updated it last year and you've got me wondering now. Before I do anything drastic, here's what I see in Windows Control Panel. Can you tell from this if it's maybe Git for Windows?

[Sven Strickroth]

Hi,

that's Git for Windows.

Msys2 Git would mean, you installed Msys2 and inside you installed Git.

Best,
Sven

Am 27.02.2026 um 12:06 schrieb John Emmas (johne53):
> Many thanks Sven. I realised that the reason 'git config (etc)' hasn't
> been working was because it's read-only so I've fixed that and it's
> writable now.
>
> Regarding git itself it was definitely Msys2 in the past but I updated
> it last year and you've got me wondering now. Before I do anything
> drastic, here's what I see in Windows Control Panel. Can you tell from
> this if it's maybe Git for Windows?
>

> Capture-15.png
> On Friday, February 27, 2026 at 10:19:00 AM UTC Sven Strickroth wrote:
>
> Hi,
>
> the reason is a security feature of Git (added in 2022,
> https://github.blog/2022-04-12-git-security-vulnerability-announced/

> #cve-2022-24765 <https://github.blog/2022-04-12-git-security-
> vulnerability-announced/#cve-2022-24765>)

> that checks whether the owner of a directory matches.
>
> As you mentioned, you are using FAT32m you need to define an exception:
> <https://weblog.west-wind.com/posts/2023/Jan/05/Fix-that-damn-Git-

> Unsafe-Repository <https://weblog.west-wind.com/posts/2023/Jan/05/

> <https://groups.google.com/d/msgid/>
> > tortoisegit-users/58b9cc12-f066-4243-
> > a1f2-97945a36f20dn%40googlegroups.com <http://40googlegroups.com>
> <https://groups.google.com/d/ <https://groups.google.com/d/>
> > msgid/tortoisegit-users/58b9cc12-f066-4243-
> > a1f2-97945a36f20dn%40googlegroups.com?
> utm_medium=email&utm_source=footer <http://40googlegroups.com?
> utm_medium=email&utm_source=footer>>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "tortoisegit-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to tortoisegit-us...@googlegroups.com
> <mailto:tortoisegit-us...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/

> tortoisegit-users/4530e789-f2e3-47b0-a32f-
> f1933a70cd49n%40googlegroups.com <https://groups.google.com/d/msgid/
> tortoisegit-users/4530e789-f2e3-47b0-a32f-
> f1933a70cd49n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[John Emmas (johne53)]

Okay, according to https://github.blog/2022-04-12-git-security-vulnerability-announced/#cve-2022-24765)

it looks like as long as I've set the safe.directory option (which I now have) I don't need GIT_CEILING_DIRECTORIES if I'm using

Git ver2.35.2 or later (I'm using 2.52.2). So in theory this should be working now (but it isn't...) 

Here's what I see if I try to pull from a repo:-

and here's what I see if I press either 'Yes' or 'No':-

[John Emmas (johne53)]

Sven - it might be worth repeating that I followed some instructions in a Youtube video but I only got about three quarters of the way through.

I managed to generate the keys okay but the next stage was to add them somewhere (a box with some Verify keys etc) but I couldn't find

that dialog box here.

[John Emmas (johne53)]

According to the site owners the SSH key should have been in ECDSA format. So I've created a key pair in the right format but it'd be

great if you could help me understand what to do next, Sven

[John Emmas (johne53)]

Sorry about so many posts but I've just managed to get a lot further with this...

Basically there were 2 x git repos which I couldn't access. So I decided to search for .ppk files on my system.

All except one was generated either yesterday or today (i.e. there was only one old .ppk file here). So after

all the changes from today, I applied that file to the relevant local repo and all is working again (albeit that

I haven't needed to use push yet).

So I contacted the owner of the other repo who reckons I might have been accessing it via the older method

of a User Name and Password. But is there such a feature in TortoiseGit? Or was there one in the past?

I'm wondering now if that's why I didn't update it for all those years...

[John Emmas (johne53)]

This gets barmier by the minute! BOTH repos that were originally non-working are working now

as long as I do a 'fetch' or' pull' with AutoLoad Putty Key deselected!! I'll keep an eye on things

for a few days and I'll assume that 'push' will also work when I come to need it.

Thanks for all your help, Sven