itsgoingd / itsgoingd/clockwork
Consider adding config for DataSource::removePasswords()
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6k
- Forks
- 333
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I am currently working with WordPress which uses "pwd" as the password key.
Not the end of the world - extend and override works fine.
But it would be nice if we could configure keys or patterns for keys that should be considered sensitive data and removed.
Contributor guide
No contributing guide indexed for this repository
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 locating DataSource::removePasswords() and reviewing how its current password-key handling works. Check the existing extension and override approach, then define how configurable keys or key patterns should cover cases such as WordPress's "pwd" key and verify that sensitive values are removed as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100