Comment 4 for bug 1249674

1) Windows _and_ Linux have protected "home" paths for private user data, so user A has no access to data in user B's "home" path.
I think, users will be _disoriented by current default behaviour_ of ntfs-3g - if ever noticed - at least I was, when I discovered that above rule does not anymore hold after adding new data to a Windows "home" path from Linux side.
Assume, one adds a folder "Projects" to /media/Windows/Users/A/ and then some data and later user B logs in on Windows.
Folder C:\Users\A\ is correctly is not accessible for user B but C:\Users\A\Projects\ is.
I believe, people regularly do not discover this, but if, I'm sure, they will be truly "disoriented".

Can you share a scenario, where a user could be disoriented, when a Linux created file object no more has Windows full access for anybody - even for Guest - but is only restricted to the permissions of it's parent folder, from which itself inherits it's permissions?

2) Current inherit behavior in combination with mandatory UserMapping actually has some traps, see:
http://tuxera.com/forum/viewtopic.php?f=3&t=30640&start=0&sid=421e2960a1766bcd9884ebce3183b235
http://tuxera.com/forum/viewtopic.php?f=3&t=30642&start=0&sid=5c992ba48debdecdcd6ebbe55da0bed5
With the there provided prototype patch for inheritance without UserMapping, new file objects in some Windows protected parent folder, created from Linux, have more or less the same permissions - by inheritance - as those, which were copied with Windows Explorer from an external permission-less source e.g. USB FAT volume. So I see no problem with:
- "the same exact result as Windows cannot be achieved"
- less worry on Linux protections - from Linux side there is no difference if mounted with inherit or not, in both cases all file objects have world access.