Skip to content

Conversation

@pinheadmz
Copy link
Contributor

@pinheadmz pinheadmz commented Oct 4, 2024

The configmap helm logic then adds the chart value to bitcoin.conf and to the pod metadata labels, same mechanism we currently use for rpcport. This allows chart-writers to override rpcpassword on an individual per-tank basis. When deploying a scenario, the metadata with the password is read from the metadata labels and written to warnet.json in the commander pod. Assuming namespaces limit users ability to read pod metadata, this should restrict rpc access to users in multiplayer mode.

I also changed the default password in the base chart values so if anything was hard coded we should see tests fail.

UPDATE: that was so smart of me, "password" was hard coded in the prometheus exporter

@m3dwards
Copy link
Collaborator

m3dwards commented Oct 4, 2024

All worked for me.

@m3dwards m3dwards merged commit 2fbbf8c into bitcoin-dev-project:main Oct 4, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants