-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
fix: smb: don't fail hard if we can't load acls for a file #49288
Conversation
Signed-off-by: Robin Appelman <robin@icewind.nl>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks dangerous, it means when unable to get acls it gives default rights to the user? So it may result in more rights because of some system hiccup, no?
the acl check only hides folders that users don't have access to from the file listing. Any attempt to enter the folder when the acl check is disabled/not working will result in the user seeing an empty folder. |
And seeing the folder name is not already an information leak? |
Windows has the same behavior of showing the non-readable folders |
/backport to stable30 |
/backport to stable29 |
Instead we log the error and behave as if no ACL was found.