Bitcointalk · Development of alert system

中本聪,2010 年 8 月 25 日

SN-2592 已核对来源,附原文与上下文。

阅读语言
中文译文

它无法远程执行任意操作。兴许你们有些人在回应其他帖子的人,是他们建议警报系统应该做更多事?

如果有警报,以下 json-rpc 方法会返回错误: sendtoaddress getbalance getreceivedbyaddress getreceivedbylabel listreceivedbyaddress listreceivedbylabel

其余 14 个方法照常工作。

我认为更安全的选项应该默认启用。倘若你想让你的服务器继续交易、无视「它收到的钱可能像溢出 bug 那笔钱」的警报,你可以用开关,赔了钱也别怪别人。

让警报开着的最坏情况,是你的网站停止交易,直到你升级或加上 -disablesafemode 开关。

在你的节点本该处于风险中时被临时停机吓一跳,好过被小偷偷光全部库存时吓一跳。

将来等我们很久没发现新 bug、也做过彻底的安全审查而一无所获时,可以把它放宽。我不是说这就是永远的常态。它还是 beta 软件。

ORIGINAL · 英文原文
It can't do arbitrary actions remotely.  Maybe some of you are responding to other posters who suggested the alert system should do more?

If there is an alert, the following json-rpc methods return an error:
sendtoaddress
getbalance
getreceivedbyaddress
getreceivedbylabel
listreceivedbyaddress
listreceivedbylabel

The remaining 14 methods function as normal.

I believe the safer option should be enabled by default.  If you want your server to keep trading and ignore an alert saying the money its receiving might be like the money from the overflow bug, then you can use the switch and not blame anyone else if you lose your money.

Worst case if you leave alerts enabled, your site stops trading until you upgrade or add the -disablesafemode switch.

Getting surprised by some temporary down time when your node would otherwise be at risk is better than getting surprised by a thief draining all your inventory.

Someday when we haven't found any new bugs for a long time and it has been thoroughly security reviewed without finding anything, this can be scaled back.  I'm not arguing that this is the permanent way of things forever.  It's still beta software.
来源
Bitcointalk 原始链接 ↗ 记录编号 SN-2592