-
-
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: consider all paths the user has for a share source when considering max permissions #44791
Conversation
326c31f
to
6980dae
Compare
5756ffd
to
8ce01e1
Compare
Signed-off-by: Robin Appelman <robin@icewind.nl>
8ce01e1
to
4c085ef
Compare
Signed-off-by: Robin Appelman <robin@icewind.nl>
9b0a812
to
4a72b96
Compare
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.
I cannot find it but you made a PR not long ago to use the node the user tried to share instead of the first one when checking reshare permission, is that a different fix for the same thing or two different cases?
Ok I’m not crazy I think you forced push over it in this very PR 🙈 |
Yeah that approach didn't end up working with in some cases |
/backport to stable29 |
/backport to stable28 |
To test
user1
create folder "Storage/folder" and share it read-only withuser2
user2
attempt to share "Storage/folder" with edit permissions touser3