You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no inspection of the channel creation transaction.
This means that during a channel creation, the creator could
inappropriately specify config, including items like orderer parameters,
and the ordering service would silently accept this incorrect
parameters. This is especially troublesome from a security perspective,
as a specially crafted config tx could potentially trick another user
into believe they were participating in a channel with one member when
they are actually participating with another.
This CR adds this checking by leveraging the existing underlying
authorization mechanisms of the configuration transaction. It ensures
that the creating members are not only authorized to create the channel,
but also ensures that all channel config that is set is done so in
accordance with the underlying governance for that config element. This
means that a collection of authorized ordering organizations may choose
to modifying ordering parameters in a channel creation request while a
set of application orgs would not be able to.
This CR is somewhat large due to the significant invasive nature of this
change, and that the entire end to end must be modified, not just a
single component. However, given the increase in function with decrease
in complexity, the diff stat is hopefully acceptable.
Change-Id: I9bb64d3f70d07eb8a8a4ea4893c71cf1112b4bf7
Signed-off-by: Jason Yellick <[email protected]>
Signed-off-by: Kostas Christidis <[email protected]>
0 commit comments