RE: [BUG] fatal: transport 'file' not allowed during submodule add
- From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
- Date
- Dec 28, 2022, 14:42 UTC
- Message-ID
- <011201d91aca$a5db7800$f1926800$@nexbridge.com>
- In-Reply-To
- <xmqqilhwp5g4.fsf@gitster.g>
>-----Original Message----- >From: Junio C Hamano <jch2355@gmail.com> On Behalf Of Junio C Hamano
On December 27, 2022 10:34 PM, Junio C Hamano wrote:
Show 10 quoted lines
><rsbecker@nexbridge.com> writes: > >> As of 2.39.0, I am now getting fatal: transport 'file' not allowed >> when performing a submodule add after a clone -l. The simple reproduce >> of this >> is: >> ... >> This happens for any submodule add on the same system. Some online >> research indicates that there was a security patch to git causing >> this, but I can't find it. This does not seem correct to me or how this
improves
Show 6 quoted lines
>security. >> Help please - this is causing some of my workflows to break. > >Thanks for reporting, Randall. > >This suspiciously sounds like what a1d4f67c (transport: make
`protocol.file.allow`
>be "user" by default, 2022-07-29) is doing deliberately. Taylor, does this
look like a
>corner case the 2.30.6 updates forgot to consider?
I have tried using 'git config --local protocol.file.allow always' and/or 'git config --local protocol.allow always' to get past this, without success.
--Randall