-
Notifications
You must be signed in to change notification settings - Fork 8.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FAB-1946] Rm ChainHeader from ConfigurationItem
https://jira.hyperledger.org/browse/FAB-1946 The current configuration transaction format expects a header per configuration item. This is more flexible, as it allows multiple parties to each sign subsets of a configuration, then submit it together. However, this additional workflow seems unnecessary, and it multiplies the number of required signatures. It also necessitates the computation of a digest in the channel creation request which is hard on the SDKs. (This digest computation will be removed in a later CR) For now, the ChainHeader is moved to the ConfigurationEnvelope, which means it is not included in the signature, this is insecure, but is the path of least complexity and smallest diff going forward until we reach the ultimate secure solution via FAB-1880. Change-Id: Idaf16c2afe0e2ebdd068d7b312a883a41a4a2017 Signed-off-by: Jason Yellick <jyellick@us.ibm.com>
- Loading branch information
Jason Yellick
committed
Feb 5, 2017
1 parent
bdba196
commit fda7f99
Showing
14 changed files
with
164 additions
and
179 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.