OWASP / OWASP/SecurityShepherd
Update the key returns to follow the same practice as the key checks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
I'd like to use Facebook's CTF platform in tandem with OWASP Security Shepherd- Is there a possibility of configuring the web app to allow for the same solution key to be generated for every player?
We've tried updating the hardcoded key flag to true, but it would seem that is only used for checking.
Thanks!
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 by tracing the hardcoded key flag from the solution-key checking path to the code that generates or returns keys. Confirm how the current key is produced for each player, then make generation follow the same shared-key behavior as checking. Done means every player receives the same solution key when the shared-key option is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100