-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FAB-2424] Gossip: Extract connection authInfo in comm
In the previous chapter of FAB-2424(https://gerrit.hyperledger.org/r/#/c/6393/) we took care of channel-based access control by consulting the MSP whether a given peer is eligible for a specific channel. This works for blocks that are broadcasted, and also for blocks that are pulled from peers in the gossip layer, but alas - the state transfer layer still stays bare and exposed to the mercy of malicious peers! This commit extends the protos/gossip/extensions.go:ReceivedMessage interface and replaces GetPKIID() with GetConnectionInfo() that returns: ID common.PKIidType Auth *AuthInfo: SignedData []byte Signature []byte Identity api.PeerIdentityType Using this, in the next commit I'll be able to modify the state transfer module by having the predicate it passes to the gossip layer when listening for messages from remote peers to also call the method provided by the MSP: VerifyByChannel() and in this way- to verify that the remote peer should indeed receive blocks or not. Change-Id: I9e2e6f4da430ed062a6fa12bebdfab4add6c4843 Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>
- Loading branch information
Showing
11 changed files
with
90 additions
and
44 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
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
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
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
Oops, something went wrong.