You'll notice
Useful3 Signal2
Git now runs under fixed environments that block network protocols unless the operation needs them.
What's wrong with this entry?
Anonymous. No account, no email.
GIT_ALLOW_PROTOCOLGIT_TERMINAL_PROMPT
What
Git commands now run under fixed environment maps rather than ones assembled per call. The restricted map sets GIT_ALLOW_PROTOCOL to none and GIT_TERMINAL_PROMPT to 0 so git cannot fetch over the network or prompt for credentials; a second map allows file:git:http:https:ssh where network access is intended.
Details
- Both maps point git's config graft at
/dev/null(or the platform equivalent) so repo-supplied config cannot take effect. - A separate set names git global flags that are rejected during command parsing, including
--exec-path,--git-dir,--attr-sourceand--shallow-file. - Invocations pass
safe.bareRepository=explicit, so git will not treat a stray directory as a bare repo.
Evidence
safe.bareRepository=explicit
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Git commands run for cloud seeding can no longer reach the network or prompt
Both mention allow protocol