nextcloud / nextcloud/files_lock
File-Lock can be circumvented by using rename function
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
Tested with Nextcloud v19.04, 19.20 and now 20.0.10 (on Debian 10)
When a file was locked (by clicking on the lock-icon) by someone else, the file cannot be accessed/edited.
This can be circumvented by right-click, select "rename", then the file can be opened/edited once, when closed the file is locked again.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First reproduce the lock, rename, and open/edit sequence described on Debian 10 or a comparable setup, then trace the rename and lock-handling paths. Done means a locked file remains inaccessible after renaming until it is unlocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100