Messages in this thread | | | Date | Wed, 01 Aug 2012 16:16:01 -0700 | From | Cody P Schafer <> | Subject | Re: [BUG] NTFS code doesn't sanitize folder names sufficiently |
| |
> The solution to this would be to disallow creation of files and > folders on NTFS drives containing illegal characters.
Illegal characters with respect to Windows & the like are different from Illegal characters with respect to the NTFS filesystem structure.
Looking at ntfs-3g(8) [yes, I'm aware that is a different driver that this bug is about], the section on Windows Filename Compatability says this:
[...] all characters are allowed except '/' and '\0'. This is perfectly legal on Windows, though some application may get confused. The option windows_names may be used to apply Windows restrictions to new file names.
To recap: no data will be lost due to using '\' in filenames. Some operating systems just may not be capable off accessing it.
-- Cody
| |