中本聪：JSON-RPC password（2010.07.19）

中文译文

所以是把设置文件丢进 ~/.bitcoin 目录，这样听起来更好。「未设密码」的警告里可以告诉你文件在哪、该做什么。

最流行、最常见的设置文件格式是什么？

应该考虑 HTTP basic authentication。不过实际操作中，对 web 开发者来说，研究怎么通过 HTTP 或 JSON-RPC 包装层的某个额外参数指定密码，比直接在参数列表开头塞一个额外参数更费劲。你们怎么看？HTTP basic authentication 能给我们带来什么额外好处吗？把它挪出参数列表，结果还是要在一个更深奥的地方指定它，我不确定这是净收益。

我一度被绕晕了，因为密码在命令行上是最后给，在 JSON-RPC 参数列表里却是第一个。我同意从文件里读命令行密码会更方便、更安全。

你也把我绕晕了，什么意思？我做了什么 unintended 的事吗？

ORIGINAL · 英文原文

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?

上下文

← 上一条 SN-1423 · 当前下一条 → 在档案中查看完整主题串 →

来源

Bitcointalk 原始链接 ↗ 记录编号 SN-1423

中本聪，2010 年 7 月 19 日