News for hackers. Stuff that matters.
Re:Git client vulnerability announced by SSLy on Thursday December 18, 2014 @08:11PM (#8770672)
My quick an dirty (pun intended) experiment concluded that ntfs, while mounted on linux, is case-sensitive. Windows will happily list all files from fs in explorer, whatever case they are, but treat them as one. And this is deep in win32: http://i.imgur.com/sWnCMdq.png (that's cygwin, while on linux, I've put a `small` file in the `test` dir).
Re:Git client vulnerability announced by ethomson on Thursday December 18, 2014 @09:31PM (#8770862)
You can mount NTFS case sensitive, but you probably don't want case sensitivity if you interop with Windows and, if you don't, why on earth would you use NTFS?
Re:Git client vulnerability announced by hoov on Thursday December 18, 2014 @10:42PM (#8771010)
Yeah. NTFS is case preserving, not case sensitive.
Re:Git client vulnerability announced by barrkel on Friday December 19, 2014 @04:55AM (#8771634)
NTFS is case sensitive. The Win32 layer presents NTFS as case preserving, but the NT POSIX layer (since renamed to SFU), as well as Cygwin, use NTFS's case sensitivity.
Re:Git client vulnerability announced by ygra on Friday December 19, 2014 @06:29AM (#8771831)
More to the point, the NTFS API can be both. And you can access that from Win32 code as well. There's also a registry flag to make NTFS case-sensitive by default.
Re:Git client vulnerability announced by im3w1l on Thursday December 18, 2014 @10:47PM (#8771021)
Anyone knows what happens if an NTFS partition has both fiLe and file, when used in windows?
Re:Git client vulnerability announced by gizmo686 on Friday December 19, 2014 @01:09AM (#8771291)
I just quickly tested this on Windows 7. It showed both a directory for both spelling, but both of them contained the same content corresponding to one of the two directories.