-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Btcd's default for rpc listening is insecure #218
Comments
This is not accurate. If there is no Are you sure you're not seeing the Bitcoin peer server output message and thinking that is the RPC server? Here is the output with no configuration file at all:
Note those last two lines are the Bitcoin peer server, not the RPC server. The RPC server is not running at all here because the
As you can see, the RPC server is only listening on localhost IPv4 and IPv6. |
I just looked at the sample config file and noticed the comment in there is wrong. Is that what you are referring to? It actually does only listen on localhost by default. |
Yes, exactly. Sorry, I thought that I observed this on the daemon and tried to verify in the docs. This issue then only concerns https://github.com/conformal/btcd/blob/master/sample-btcd.conf#L160 |
The documentation has been updated by pull request #220. |
…data-from-msgtx wire, electrum, netsync, wallet, main: remove udata from MsgTx
Currently, btcd listens to all interfaces once rpc is enabled. This is potentially insecure. I would propose
127.0.0.1
as a sensible default, similar to the behavior of Bitcoin Core.If not, this important difference must be specified in #208
The text was updated successfully, but these errors were encountered: