Re: safe directory on shared drives

From: Philip Oakley <philipoakley@iee.email>
Date: Apr 15, 2022, 12:02 UTC
Message-ID: <488bf3f0-7859-7b7c-b46d-48248aacca62@iee.email>
In-Reply-To: <CAO=QCg6+J-dA2U9F5dseKbb=HA_pLFmZ9tbHydnLRSk5Dg2UXg@mail.gmail.com>

Glad it worked! copying in the list in case others can be helped by the confirmation. P.

On 15/04/2022 12:55, Andrew Noblet wrote:

Show 63 quoted lines

> Thank you! Adding `git config --global --add safe.directory
> '%(prefix)///192.168.0.120/config/'` <http://192.168.0.120/config/'`>
> worked!
>
> Andrew
>
> On Fri, Apr 15, 2022 at 7:43 AM Philip Oakley <philipoakley@iee.email>
> wrote:
>
>     Hi Andrew,
>
>     On 15/04/2022 11:14, Andrew Noblet wrote:
>     > The new git security rules creates an issue on Windows systems where
>     > the git repository is hosted in a shared folder.
>     >
>     > $ git status
>     >
>     > ```
>     > fatal: unsafe repository ('//192.168.0.120/config/
>     <http://192.168.0.120/config/>' is owned by someone else)
>     > To add an exception for this directory, call:
>     >
>     >         git config --global --add safe.directory
>     //192.168.0.120/config/ <http://192.168.0.120/config/>
>     > ```
>     >
>     > $ git config --global --add safe.directory
>     //192.168.0.120/config/ <http://192.168.0.120/config/>
>     > $ git status
>     >
>     > ```
>     > warning: encountered old-style '//192.168.0.120/config/
>     <http://192.168.0.120/config/>' that should
>     > be '%(prefix)//192.168.0.120/config/ <http://192.168.0.120/config/>'
>     > fatal: unsafe repository ('//192.168.0.120/config/
>     <http://192.168.0.120/config/>' is owned by someone else)
>     > To add an exception for this directory, call:
>     >
>     >         git config --global --add safe.directory
>     //192.168.0.120/config/ <http://192.168.0.120/config/>
>     > ```
>     >
>     > There seems to be no way to add a shared drive path to the safe
>     directory list.
>
>     This (instruction clarification) is being discussed / sorted at
>     [git-for-windows/git] Include trailing slash in prefix migration
>     instructions (PR #3790)
>     https://github.com/git-for-windows/git/pull/3790
>
>     The key point being that for a `//server` path you will need three
>     slashes. (IIUC) One for magic prefix string, and then two as part
>     of the
>     server name.
>
>     There is now also the `*` option that permits all as safe
>     directories. 
>     Worth checking how the user and group security is being handled
>     locally,
>     especially for accidental failures.
>     Philip
>
>