Re: safe.directory wildcards

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 29, 2024 at 09:02:16AM GMT, Junio C Hamano wrote:
> When safe.directory was introduced in v2.30.3 timeframe, 8959555c
> (setup_git_directory(): add an owner check for the top-level
> directory, 2022-03-02), it only allowed specific opt-out
> directories.  Immediately after an embargoed release that included
> the change, 0f85c4a3 (setup: opt-out of check with safe.directory=*,
> 2022-04-13) was done as a response to loosen the check so that a
> single '*' can be used to say "I trust all repositories" for folks
> who host too many repositories to list individually.
> 
> Let's further allow people to say "everything under this hierarchy
> is deemed safe" by specifying such a leading directory with "/*"
> appended to it.

I welcome this change, too!

Acked-by: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>

-K




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux