I'm struggling to understand the process that went into this "feature" existing. It seems the most likely candidate is a developer's git started malfunctioning and an agent "fixed" it by dropping a `git.exe` in the repo and then conditionally calling it when it exists.

▲

gruez 4 hours ago | parent | next [-]

>It seems the most likely candidate is a developer's git started malfunctioning and an agent "fixed" it by dropping a `git.exe` in the repo and then conditionally calling it when it exists.

It doesn't need to be that deliberate. The default shell on windows (cmd.exe) includes the current directory into PATH by default. In other words, you don't need to do `./program.exe`, `program.exe` would suffice. That's probably where the bug came from. This also means if you were using cmd.exe, ran `git clone`, went inside it, then executed any command (eg. dir or git) you could get pwned.

▲

drdexebtjl 4 hours ago | parent [-]

Windows doesn’t really have a default login shell like Unix.

Windows Terminal defaults to PowerShell which does not suffer from this issue.

	▲	inigyou an hour ago \| parent [-]
		Windows has a default login shell which is explorer.exe. Windows also has a system(const char) which certainly does something.*

▲

conartist6 4 hours ago | parent | prev [-]

and ever since, this approach has been a critical pathway for some billion dollar business probably. hooray

	▲	pixl97 4 hours ago \| parent [-]
		I see you also work in enterprise software.