a little filename weirdness
I ran the following commands in WSL with PWD the home directory of an added user account.
echo 1 > aa
echo 12 > aA
echo 123 > Aa
echo 1234 > AA
In WSL ls shows 4 different files, and cat displays each of them as expected.
Then using Windows's CMD.EXE with the same working directory, the dir command shows 4 files named the same as under WSL, but the command type aa produces the output
1
1
1
1
Windows expects case-insensitive filenames. It sees 4 files named aa given case-insensitivity, and it seems to respond by displaying the aa file 4 times. Interesting possible way to hide files in plain sight.
Also problems with filenames containing valid chars under Linux but not allowed in Windows filenames. WSL seems to use UNICODE encodings of chas Windows doesn't support, so the valid Linux filename a:b becomes a#003Ab when listing the file under Windows.
Posted Aug 8, 2016, 8:11 PM UTC
[deleted]