stackabletech / stackabletech/druid-operator
[Security] Check if druid.client.https.validateHostnames can be turned of
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 1
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 10
Description
Affected version
nightly
Current and expected behavior
Currently we set druid.client.https.validateHostnames and druid.server.https.validateHostnames to false which imposes a security risk.
We should get rid of it.
Context: https://github.com/stackabletech/druid-operator/blob/d4477a5e8c802bd1059e592c82fd1632a3aef63a/rust/crd/src/security.rs#L330-L336
Possible solution
No idea, needs testing
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
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 with rust/crd/src/security.rs around lines 330-336 and inspect how druid.client.https.validateHostnames and druid.server.https.validateHostnames are configured. Test the affected Druid deployment behavior and determine what configuration is needed to remove the insecure false settings. Done means the settings are no longer forced to false and relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100