Open thesoftwarejedi opened 9 years ago
Yes, i have already had some thoughts about it: It can be easily solved by adding the allowed signers public key and sign to content.json like this:
"signers": [
{"Signer1Addr": "Signer1sign"},
{"Signer2Addr": "Signer2sign"},
{"Signer3Addr": "Signer3sign"}
],
"signers_required": 2,
So when someone got a new content.json, he checks if it has the required number (definied in signers_required
) of correct signs.
Maybe we should combine it with some kind of permission system, so you could define rules like: "Signer4Addr" has permission to modify "messages/Signer4Addr.json" file, but not anything else. (size could be possible limit too)
But at the moment I want to keep ZeroNet as simple as possible, and only adding new features if we has the application that could use benefits of it.
Its implemented in 0.2.0, but its not deep tested yet
Can be closed?
Can be closed?
ContentManager.py:460 Still not implemented
not implemented yet
@ArchisGokhale read the scribe post for context, multisig is possible with current code.
future enhancement. When publishing becomes popular, more security should be allowed at the site key level in the form of multisig or scriptsig of some type.