How can I ensure that all organizations have signed the chaincode to install?
In Hyperledger Fabric 1.3,
how can I ensure that all organizations have signed the chaincode to install ?
I could sign the code, but it seems that no component verifies the signature.
Details are as below:
Preconditions
- Fabric 1.3
- I have two orgs, org1 and org2.
- org1 wants to verify that org2 has signed the code, and vice versa, for non-repudiation (undeniability).
- I know that we can install chaincode without signatures by
peer chaincode install.
Expected Behaviour
In the below Commands, I expected that:
- Option A must succeed, because the chaincode includes signatures from both orgs.
- Option B must produce some kind of error or warning, because the chaincode lacks a signature from org2.
Actual Behaviour
- Not only Option A but B also succeeds with no errors, which is against the expectation.
Commands
org1> peer chaincode package -n mycc -v 0 example02/cmd -s -S
-i "AND('Org1MSP.admin')" cc.out
Option A:
org2> peer chaincode signpackage cc.out signedcc.out
org1> peer chaincode install -n mycc -v 0 signedcc.out
org2> peer chaincode install -n mycc -v 0 signedcc.out
Option B:
org1> peer chaincode install -n mycc -v 0 cc.out
org2> peer chaincode install -n mycc -v 0 cc.out
org1> peer chaincode instantiate -o orderer:7050 -C mychannel
-n mycc -v 0 -c '(snip)' -P "AND ('Org1MSP.peer','Org2MSP.peer')"
# Then Org2 makes a query.
The flow
hyperledger-fabric hyperledger blockchain
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
add a comment |
In Hyperledger Fabric 1.3,
how can I ensure that all organizations have signed the chaincode to install ?
I could sign the code, but it seems that no component verifies the signature.
Details are as below:
Preconditions
- Fabric 1.3
- I have two orgs, org1 and org2.
- org1 wants to verify that org2 has signed the code, and vice versa, for non-repudiation (undeniability).
- I know that we can install chaincode without signatures by
peer chaincode install.
Expected Behaviour
In the below Commands, I expected that:
- Option A must succeed, because the chaincode includes signatures from both orgs.
- Option B must produce some kind of error or warning, because the chaincode lacks a signature from org2.
Actual Behaviour
- Not only Option A but B also succeeds with no errors, which is against the expectation.
Commands
org1> peer chaincode package -n mycc -v 0 example02/cmd -s -S
-i "AND('Org1MSP.admin')" cc.out
Option A:
org2> peer chaincode signpackage cc.out signedcc.out
org1> peer chaincode install -n mycc -v 0 signedcc.out
org2> peer chaincode install -n mycc -v 0 signedcc.out
Option B:
org1> peer chaincode install -n mycc -v 0 cc.out
org2> peer chaincode install -n mycc -v 0 cc.out
org1> peer chaincode instantiate -o orderer:7050 -C mychannel
-n mycc -v 0 -c '(snip)' -P "AND ('Org1MSP.peer','Org2MSP.peer')"
# Then Org2 makes a query.
The flow
hyperledger-fabric hyperledger blockchain
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
add a comment |
In Hyperledger Fabric 1.3,
how can I ensure that all organizations have signed the chaincode to install ?
I could sign the code, but it seems that no component verifies the signature.
Details are as below:
Preconditions
- Fabric 1.3
- I have two orgs, org1 and org2.
- org1 wants to verify that org2 has signed the code, and vice versa, for non-repudiation (undeniability).
- I know that we can install chaincode without signatures by
peer chaincode install.
Expected Behaviour
In the below Commands, I expected that:
- Option A must succeed, because the chaincode includes signatures from both orgs.
- Option B must produce some kind of error or warning, because the chaincode lacks a signature from org2.
Actual Behaviour
- Not only Option A but B also succeeds with no errors, which is against the expectation.
Commands
org1> peer chaincode package -n mycc -v 0 example02/cmd -s -S
-i "AND('Org1MSP.admin')" cc.out
Option A:
org2> peer chaincode signpackage cc.out signedcc.out
org1> peer chaincode install -n mycc -v 0 signedcc.out
org2> peer chaincode install -n mycc -v 0 signedcc.out
Option B:
org1> peer chaincode install -n mycc -v 0 cc.out
org2> peer chaincode install -n mycc -v 0 cc.out
org1> peer chaincode instantiate -o orderer:7050 -C mychannel
-n mycc -v 0 -c '(snip)' -P "AND ('Org1MSP.peer','Org2MSP.peer')"
# Then Org2 makes a query.
The flow
hyperledger-fabric hyperledger blockchain
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
In Hyperledger Fabric 1.3,
how can I ensure that all organizations have signed the chaincode to install ?
I could sign the code, but it seems that no component verifies the signature.
Details are as below:
Preconditions
- Fabric 1.3
- I have two orgs, org1 and org2.
- org1 wants to verify that org2 has signed the code, and vice versa, for non-repudiation (undeniability).
- I know that we can install chaincode without signatures by
peer chaincode install.
Expected Behaviour
In the below Commands, I expected that:
- Option A must succeed, because the chaincode includes signatures from both orgs.
- Option B must produce some kind of error or warning, because the chaincode lacks a signature from org2.
Actual Behaviour
- Not only Option A but B also succeeds with no errors, which is against the expectation.
Commands
org1> peer chaincode package -n mycc -v 0 example02/cmd -s -S
-i "AND('Org1MSP.admin')" cc.out
Option A:
org2> peer chaincode signpackage cc.out signedcc.out
org1> peer chaincode install -n mycc -v 0 signedcc.out
org2> peer chaincode install -n mycc -v 0 signedcc.out
Option B:
org1> peer chaincode install -n mycc -v 0 cc.out
org2> peer chaincode install -n mycc -v 0 cc.out
org1> peer chaincode instantiate -o orderer:7050 -C mychannel
-n mycc -v 0 -c '(snip)' -P "AND ('Org1MSP.peer','Org2MSP.peer')"
# Then Org2 makes a query.
The flow
hyperledger-fabric hyperledger blockchain
hyperledger-fabric hyperledger blockchain
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
edited Nov 26 '18 at 9:22
ŌHARA Kazutaka
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
asked Nov 22 '18 at 6:41
ŌHARA KazutakaŌHARA Kazutaka
517
517
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is currently no enforcement of signed chaincode packages within Hyperledger Fabric. In version 2.0 (targeted for late March), there will be a new lifecycle for chaincode which will provide this type of functionality.
For the current 1.3 and upcoming 1.4 releases, it will be up to the organization installing the chaincode to check that they have the right / enough signatures for the chaincode package prior to installing.
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425198%2fhow-can-i-ensure-that-all-organizations-have-signed-the-chaincode-to-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is currently no enforcement of signed chaincode packages within Hyperledger Fabric. In version 2.0 (targeted for late March), there will be a new lifecycle for chaincode which will provide this type of functionality.
For the current 1.3 and upcoming 1.4 releases, it will be up to the organization installing the chaincode to check that they have the right / enough signatures for the chaincode package prior to installing.
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
add a comment |
There is currently no enforcement of signed chaincode packages within Hyperledger Fabric. In version 2.0 (targeted for late March), there will be a new lifecycle for chaincode which will provide this type of functionality.
For the current 1.3 and upcoming 1.4 releases, it will be up to the organization installing the chaincode to check that they have the right / enough signatures for the chaincode package prior to installing.
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
add a comment |
There is currently no enforcement of signed chaincode packages within Hyperledger Fabric. In version 2.0 (targeted for late March), there will be a new lifecycle for chaincode which will provide this type of functionality.
For the current 1.3 and upcoming 1.4 releases, it will be up to the organization installing the chaincode to check that they have the right / enough signatures for the chaincode package prior to installing.
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
There is currently no enforcement of signed chaincode packages within Hyperledger Fabric. In version 2.0 (targeted for late March), there will be a new lifecycle for chaincode which will provide this type of functionality.
For the current 1.3 and upcoming 1.4 releases, it will be up to the organization installing the chaincode to check that they have the right / enough signatures for the chaincode package prior to installing.
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
answered Nov 30 '18 at 15:12
Gari SinghGari Singh
4,1902518
4,1902518
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
add a comment |
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
In the case the org wish to check the signatures, how will they achieve that ? I couldn't find something like ` peer chaincode verify`.
– ŌHARA Kazutaka
Dec 3 '18 at 9:28
1
1
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
Unfortunately, we never implemented that so you would need to write the code to do that yourself. If you look at github.com/hyperledger/fabric/blob/release-1.3/core/common/… it shows how the signature is created and github.com/hyperledger/fabric/blob/release-1.3/core/common/… shows how the signed install package (with detached signatures) is created.
– Gari Singh
Dec 3 '18 at 11:08
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425198%2fhow-can-i-ensure-that-all-organizations-have-signed-the-chaincode-to-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
