diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-09-05 13:44:21 +0200 |
---|---|---|
committer | Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-12-05 15:37:06 +0100 |
commit | 817ddd64c20b29b2d86b3a0589f7ff88d1279109 (patch) | |
tree | 8aad21a3b28345494fbdfe71aed52d38ad5e29ae /sigchain.c | |
parent | mingw: refuse to access paths with trailing spaces or periods (diff) | |
download | tgif-817ddd64c20b29b2d86b3a0589f7ff88d1279109.tar.xz |
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>
Diffstat (limited to 'sigchain.c')
0 files changed, 0 insertions, 0 deletions