mingw: refuse to access paths with illegal characters
Certain characters are not admissible in file names on Windows, even if Cygwin/MSYS2 (and therefore, Git for Windows' Bash) pretend that they are, e.g. `:`, `<`, `>`, etc Let's disallow those characters explicitly in Windows builds of Git. Note: just like trailing spaces or periods, it _is_ possible on Windows to create commits adding files with such illegal characters, as long as the operation leaves the worktree untouched. To allow for that, we continue to guard `is_valid_win32_path()` behind the config setting `core.protectNTFS`, so that users _can_ continue to do that, as long as they turn the protections off via that config setting. Among other problems, this prevents Git from trying to write to an "NTFS Alternate Data Stream" (which refers to metadata stored alongside a file, under a special name: "<filename>:<stream-name>"). This fix therefore also prevents an attack vector that was exploited in demonstrations of a number of recently-fixed security bugs. Further reading on illegal characters in Win32 filenames: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This commit is contained in:
@ -431,8 +431,11 @@ int mingw_offset_1st_component(const char *path);
|
||||
/**
|
||||
* Verifies that the given path is a valid one on Windows.
|
||||
*
|
||||
* In particular, path segments are disallowed which end in a period or a
|
||||
* space (except the special directories `.` and `..`).
|
||||
* In particular, path segments are disallowed which
|
||||
*
|
||||
* - end in a period or a space (except the special directories `.` and `..`).
|
||||
*
|
||||
* - contain any of the reserved characters, e.g. `:`, `;`, `*`, etc
|
||||
*
|
||||
* Returns 1 upon success, otherwise 0.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user