Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access rights to files/folders (randomly?) return incorrect value, no matter if "no_acs_rules", usmask, fmask/dmask is set #5

Open
systemofapwne opened this issue Aug 17, 2021 · 4 comments

Comments

@systemofapwne
Copy link

systemofapwne commented Aug 17, 2021

When specifically mounting an NTFS drive with noacsrules, one can indeed write to files and folders, no matter what their respective NTFS permissions are.
However, when doing an ls, some folders and files return incorrect permissions from time to time like r-xr-xr-x.
This becomes problematic, whenever a program stat that directory/file and sees, that there is no w flag so it denies write access to it (even though it could according to noacsrules). Take e.g. a file manager like Dolphin: "right click/Create" is grayed out.

I expected permission masks to be the problem, but settings umask=0000 (same for f/dmask) do not fix the problem.

As a comparison between ntfs3 and ntfs-3g:

  • When mounting via ntfs-3g with the options rw,user,exec,uid=1000,gid=1000,umask=0000,fmask=0000,dmask=0000, all files and folders are set correctly to rwxrwxrwx.
drwxrwxrwx 1 klaus klaus        4096  9. Mai 21:53  Server
drwxrwxrwx 1 klaus klaus           0  4. Apr 07:03  SpeechRecognition
drwxrwxrwx 1 klaus klaus        4096 27. Mai 23:52  Spiele
  • When mounting via ntfs3 with the options rw,user,exec,uid=1000,gid=1000,noacsrules,umask=0000,fmask=0000,dmask=0000, I see this:
dr-xr-xr-x 1 klaus klaus        4096  9. Mai 21:53  Server
drwxrwxrwx 1 klaus klaus           0  4. Apr 07:03  SpeechRecognition
dr-xr-xr-x 1 klaus klaus        4096 27. Mai 23:52  Spiele

Note, that not all folders are missing the write-flag.
Also note, that ntfs-3g with no mount options set at all still shows these folders to be accessible as rwxrwxrwx

System Information
OS: Manjaro
Kernel: 5.10.59-1-MANJARO (LTS)
ntfs3 driver: https://aur.archlinux.org/packages/ntfs3-dkms-git/

@systemofapwne
Copy link
Author

systemofapwne commented Aug 19, 2021

I even think, that there is a general problem with permissions for this driver. I just booted up my Windows system to check the permissions. They are all equal for the shown folders, as you can see on this screenshot.

ntfs3_permissions_windows

However, ntfs3 reports them incorrectly as stated in the initial bugreport.

@abarton5
Copy link

I confirm I had this problem when mounting my windows partition.

@systemofapwne
Copy link
Author

Hi.
This bug is not yet fixed. I tested this behaviour for different kernels (5.10, 5.14) and several configurations (noacl, noacsrules).
On top of it, this repo might be the wrong location to ask for awareness. The official "repo" of the linux kernel including the changes of paragon (maintained by paragaon) can be found here https://github.com/Paragon-Software-Group/linux-ntfs3
However, you can't report bugs there. I guess, discussion about the development happens via the kernel mailing list. But I'm unsure about how to approach it.

@systemofapwne
Copy link
Author

systemofapwne commented May 13, 2023

Bug still persist with kernel 6.1. Even though ntfs3 is way superious to ntfs-3g, it stays unusable for me with the permissions not reflecting how they should be set.
Further more, the owner of some folders seem to stay "root" rather than the uid/gid that is set via mount options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants