原始文献 / 论坛帖 / Re: Development of alert system
Re: Development of alert system
Bitcointalk · 2010-08-25 15:17:37 UTC
它无法远程执行任意操作。也许你们中的一些人是在回应其他发帖者——他们建议警报系统应该做得更多？
如果出现警报，以下 json-rpc 方法将返回错误：
sendtoaddress
getbalance
getreceivedbyaddress
getreceivedbylabel
listreceivedbyaddress
listreceivedbylabel
其余 14 个方法照常运行。
我认为更安全的选项应该默认启用。如果你想让你的服务器继续交易、无视警报——警报说它收到的钱可能像溢出漏洞产生的钱——那你可以使用这个开关；万一丢了钱，别怪别人。
最坏的情况是：你保持警报启用，你的网站会停止交易，直到你升级或加上 -disablesafemode 开关。
当你的节点本来就处于风险中时，遭遇一次意外的短暂停机，总比遭遇小偷掏空你所有库存要好。
将来某天，当我们很久都没有再发现新 bug，并且它已经过彻底的安全审查而一无所获时，可以再放宽。我并不是说这是永远不变的永久方案。这仍然是测试版软件。
英文原文
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.