问题描述
在将数据存储到Fabric中之前对其进行哈希处理.我的结构应用程序使用Couchdb.当我打开沙发床所在的端口时，它以JSON格式显示了可以修改的数据，那么如何防止这种修改呢?
Data is hashed before getting stored in the Fabric. My fabric application uses Couchdb. When I opened the port on which couchdb is live , it showed data in JSON format which could be modified so how can I prevent this modification??
最重要的是，散列数据存储在Fabric应用程序中的什么位置???????
and most importantly where is the hashed data stored in Fabric application???????
推荐答案
您无法阻止这种修改，因为您可以连接到CouchDB，您基本上可以重写所有内容，而实际上没有人可以阻止您.话虽这么说，但有了强有力的认可政策，您实际上可以减轻此类数据篡改的影响.例如，如果您可以将认可政策定义为
You cannot prevent such modification since one you able to get connected to the CouchDB you basically able to rewrite everything and no one actually could prevent you. However that being said, with strong endorsement policy you can actually mitigate the influence of such data tampering. For example if you can define endorsement policy to be
AND(Org1.member, Org2.member)
并说有人伪造了Org1的认可对等方并更改了CouchDB中的记录，则执行认可的应用程序将能够检测到认可响应的不一致.例如，要使其更强大，您可以定义认可策略，该策略需要每个组织的两个同级之间的认可，从而使攻击者成功的可能性较小.
and say someone forged endorsing peer of the Org1 and changed record in CouchDB, application doing endorsement will be able to detect inconsistency of the endorsement response. For example to make it even stronger you can define endorsement policy which will require endorsement from two peers of each organization, therefore making it less likely for attacker to succeed.
存储在区块链中而不是状态DB中的哈希数据，状态DB仅反映最近的块提交接受的更改.
The hashed data stored in the blockchain, not in the state DB, state DB only reflects changes accepted by recent block commit.
这篇关于Hyperledger Fabric中的数据存储的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！