回复：JSON-RPC 密码
原始发布页
打开来源页面查看 1 个交叉存档
也就是说，你把一个设置文件放进 ~/.bitcoin 目录，这听起来更好。在“未设置密码”的警告中，可以告诉你文件在哪里以及该怎么做。
最流行、最常见的设置文件格式是什么？
应该考虑 HTTP 基本认证。不过在实际操作中，对 Web 开发者来说，弄清楚如何通过 HTTP 或 JSON-RPC 封装器中的某个额外参数指定密码，比直接在参数列表开头加一个额外参数更麻烦。你怎么看？HTTP 基本认证能给我们带来什么额外好处吗？把它从参数列表中移走，却仍然必须在一个更隐晦的位置指定它，我不确定总体上是否更好。
引用 gavinandresen 于 2010 年 7 月 19 日中午 12:02:39 的发言
我困惑了一会儿，因为密码在命令行中放在最后，但在 JSON-RPC 参数列表中却放在最前。我同意，从文件中读取命令行密码会更方便，也更安全。
你也把我弄糊涂了，你是什么意思？我是不是无意中做了什么？
英文原文
展开英文原文
So you drop a settings file in the ~/.bitcoin directory, that sounds better. In the "no password is set" warning, it could tell you where the file is and what to do.
What is the most popular and common settings file format?
HTTP basic authentication should be considered. In actual practice though, it's more work for web developers to figure out how to specify the password through some extra parameter in the HTTP or JSON-RPC wrapper than to just stick an extra parameter at the beginning of the parameter list. What do you think? Does HTTP basic authentication get us any additional benefits? Moving it off the parameter list but then you still have to specific it in a more esoteric place I'm not sure is a net win.
Quote from: gavinandresen on July 19, 2010, 12:02:39 PM
I was confused for a bit because the password is given LAST on the command line, but FIRST in the JSON-RPC params list. I agree that reading the command-line password from a file would be more convenient and more secure.
You're also confusing me, what do you mean? Did I do something unintended?