回复：警报系统的开发
原始发布页
打开来源页面查看 1 个交叉存档
它无法远程执行任意操作。也许你们当中有些人是在回应其他发帖者提出的、警报系统应该做得更多的建议？
如果有警报，以下 json-rpc 方法会返回错误： sendtoaddress getbalance getreceivedbyaddress getreceivedbylabel listreceivedbyaddress listreceivedbylabel
其余 14 个方法照常运行。
我认为更安全的选项应当默认启用。如果你希望服务器继续交易，并忽略一条声称其收到的钱可能与溢出漏洞产生的钱类似的警报，那么你可以使用该开关；如果你损失了钱，就不要责怪其他任何人。
如果你保持启用警报，最坏的情况是你的网站停止交易，直到你升级或添加 -disablesafemode 开关。
当你的节点本会面临风险时，因一段临时停机而感到意外，总好过因小偷掏空你的全部库存而感到意外。
将来有一天，当我们很久都没有发现任何新漏洞，而且它经过彻底的安全审查也没有发现任何问题时，可以再收缩这一机制。我并不是说这永远都会是事物的固定运作方式。它仍然是测试版软件。
英文原文
展开英文原文
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.