** Summary changed: - forbidden characters is filenames are allowed + ntfs treated by default as POSIX
** Description changed: Binary package hint: ntfs-3g version 1:1.616-1 - The windows filesystem has some forbidden characters such as + The ntfs filesystem in a default windows istallation has some forbidden characters such as : \ ? and others (I don't have the list) + and is not case sensitive Using ntfs3g it is possible to create files with this names. Those files - cannot be read in windows. + cannot be read in windows, without Windows Services for Unix. - Such as the kernel driver "vfat", ntfs-3g has to forbid the creation of - files with these characters in the name + We are evaluating if ntfs-3g should behave like the old vfat driver that forbids the creation of these files, or should stay by default POSIX. + Anyway I think that ntfs-3g needs an option to control this behaviour + + NOTE: microsoft developer ntfs as a POSIX filesystem for interoperability, but added these restrictions in windows to support legacy apps, and because they think that accessing a case sensitive filesystem is a security risk, because the user could execute the troyan EDIT.exe instead of edit.exe (I do not really understand this, but it is reported in the help of Windows Services for Unix) + A windows installation with Windows Services for Unix is not able to manage files which only differ by case, using normal software such as explorer. The appropriate programs installed by WSfU must be used. -- ntfs treated by default as POSIX https://bugs.launchpad.net/bugs/124480 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
