nextcloud / nextcloud/files_accesscontrol
Not blocking shared resource by its name
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 60
- Forks
- 22
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 34
Description
I am trying to forbid access to a folder by its name, so I've created a rule Filename contains /FolderName/.
So, it works if
- the folder is local
- the folder is a subfolder of a shared resource
And it doesn't work if it is the name of a shared folder of the upper level.
Please, fix it to let the shared folders can be filtered by filename.
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. Reproduce the Filename contains /FolderName/ rule against a local folder, a subfolder of a shared resource, and a top-level shared folder; done means the rule also blocks access to the top-level shared folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100