Closed d6n13l0l1v3r closed 3 months ago
I looked at this and realized it may easily fixable than I initially thought. I'm wondering how the config looks in the other services you mention. Do you simply specify either user/pass or the file path, or does it default to use the cookie if the user/pass is not provided?
You only specify the path for cookie file Example
/data/bitcoin/.cookie
@sr-gi I don't know if you can see this as reference https://github.com/golden-guy/ckpool-solo/commit/3df23a6f4335591fc6f48de394d1b16df995dbdd
@d6n13l0l1v3r would you mind giving https://github.com/talaia-labs/rust-teos/pull/249 a go? The final version may slightly vary due to code review, but I'd like to know if this has the expected UX
sure I will test it as soon arrive to master until now I can download
You can test it by creating a separate branch and pulling from the PR branch:
git checkout -b rpcauth-patch
git pull https://github.com/sr-gi/rust-teos.git 2024-01-authcookie
on it
I comment the user and password to test btc_rpc_cookie
start daemon
until now all looks fine
confirm that after one new block arrive teos receive it as expect
for me the change is ok
Let's keep this open until #249 is merged.
I would like to work on this.
I would like to work on this.
Check the linked PR. This has already been addressed, it just needs merging
Description
In order to avoid username/passwords which are not the recommended config for bitcoind it would be great if i could import the rpccookiefile for bitcoind instead of using user/pass
Problem to be solved
corelíghthing, fulcrum , electrs, and most other tools i use utilize the cookie file to avoid using a static user:pass, but I'm unable to use rust-toes with this configuration because it appears as though there is no support for the cookie file
Proposed solution
allow rust-toes to use the cookie file for bitcoind rpc authentication