nextcloud / nextcloud/nextcloud-docker-dev
Improve initial setup to trigger more bugs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
As @nickvergessen mentioned there could be a couple of things to configure to trigger bugs
-
Set a displayname on the users, maybe displaynames with some xss teststrings
-
File skeleton with special characters
-
TODO: Collect more
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
Start with the repository's docker-compose development-environment setup and identify where initial users and the file skeleton are configured. Add display names containing XSS test strings and file-skeleton names with special characters, then verify that the setup exposes bugs; the remaining TODO cases are not yet defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, php
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100