News for hackers. Stuff that matters.
Re:WSL2 corrupting Git repositories and shell history by jan6 on Saturday January 02, 2021 @07:17PM (#25618045)
because windows has no concept of an executable bit, so a rename could make it runnable? or a benign looking program has a built-in interpreter run code from external file?
Re:WSL2 corrupting Git repositories and shell history by dataflow on Saturday January 02, 2021 @08:23PM (#25618452)
> windows has no concept of an executable bit

Sure it does. Execution is a permission you can set in the security tab.

> a rename could make it runnable

This is more likely why.

Re:WSL2 corrupting Git repositories and shell history by samb1729 on Sunday January 03, 2021 @04:02AM (#25620594)
> because windows has no concept of an executable bit, so a rename could make it runnable

This much I understand - but why can something so tightly integrated into the OS not instead intercept a file rename event and scan at that point?

I seem to be lacking sufficient information as to what specifically about Windows necessitates scanning everything on the filesystem when macOS and the various common Linux distros seem to do fine without it. It's not as if Windows is the only OS with interpreters, either.