You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But then the next check allows to unlock, because the file is created inside the shared directory it is owned implicitly by the sharing user, and we allow file owners always to unlock:
Scenario:
User A creates a shared directory.
User B creates a file in that directory and locks the file
User A tries to unlock that file.
What happens:
The file gets unlocked without errors.
What should happen / is expected:
The file stays locked and the server returns 403. Because the lock is owned by user B.
Why does this happen
The initial test if the owner of the lock and the current user are the same, fails ✔️
files_lock/lib/Service/LockService.php
Line 244 in 7b1827a
But then the next check allows to unlock, because the file is created inside the shared directory it is owned implicitly by the sharing user, and we allow file owners always to unlock:
files_lock/lib/Service/LockService.php
Line 248 in 7b1827a
I am not sure if this is a feature or a bug. So probably two solutions here:
The text was updated successfully, but these errors were encountered: