Please Support SPLUNK_HASHED_PASSWORD
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
This is related to Issue #318
At the moment, SPLUNK_PASSWORD is expected in ENV or default.yml or a password file is expected.
Our Security Team is not happy with clear text password in docker-compose.yml or default.yml or /tmp/splunk-password
Please add support to SPLUNK_HASHED_PASSWORD in ENV or hashed_password in default.yml
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
Inspect how SPLUNK_PASSWORD is handled in docker-compose.yml, default.yml, and the password-file path, then review related Issue #318 for context. Done means SPLUNK_HASHED_PASSWORD in the environment and hashed_password in default.yml are supported without requiring clear-text password storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100