OWASP / OWASP/SecurityShepherd
Level Cookie Clean Up
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
Security Shepherd should clean up challenge specific cookies as they are no longer required. User's regularly get confused when they see "checksum" from one challenge in following requests.
Not sure if there needs to be a clean up utility that removes the cookies from the user's browser or if the cookies should just be set to expire inside a short time of the level page being opened
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 where challenge-specific cookies such as "checksum" are created and how level pages transition to following requests. Decide whether cleanup should remove cookies or set short expirations; done means cookies from one challenge no longer appear in later requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100