Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exercise a full end-to-end flow with PKCS11 #1717

Merged
merged 1 commit into from Aug 12, 2020

Conversation

sykesm
Copy link
Contributor

@sykesm sykesm commented Aug 12, 2020

Execute the basic query-invoke-query pattern against a solo network with BCCSP configured to use PKCS11.

Execute the basic query-invoke-query pattern against a solo network with
BCCSP configured to use PKCS11.

Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>
@sykesm sykesm requested a review from a team as a code owner August 12, 2020 17:51
@caod123 caod123 merged commit 9c7f10e into hyperledger:master Aug 12, 2020
Copy link
Contributor

@ale-linux ale-linux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a very minor nit and a question (and I now realise that in the meantime the PR already got merged but maybe you could still answer if you have a sec).

@@ -33,89 +33,106 @@ import (
"github.com/tedsuo/ifrit"
)

var _ = Describe("Configures PKCS#11 for peer and orderer", func() {
var _ = Describe("PKCS11 enabled network", func() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor but the real name of the standard is PKCS #11 (see here https://en.wikipedia.org/wiki/PKCS_11). So while the previous string was incorrect due to the missing space, your's isn't correct either. If you are okay with changing I'd change it here and everywhere else.

orgAdminMSPPath := network.PeerUserMSPDir(peer, "Admin")
updateMSPFolder(orgAdminMSPPath, fmt.Sprintf("Admin@%s-cert.pem", domain), newAdminPemCert)

By("Updating the peer user1 signcerts")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me see if I understand why you added this step: by updating the user cert (that is, the one the CLI will use to sign proposal and transaction), are you ensuring that PKCS #11 is also used by the CLI? Assuming I got this right, would you agree that this would never happen in production since proposal/tx signing will be performed by the SDK which we don't exercise here?

@sykesm sykesm deleted the bccsp-e2e branch August 12, 2020 19:18
wlahti pushed a commit to wlahti/fabric that referenced this pull request Oct 2, 2020
Execute the basic query-invoke-query pattern against a solo network with
BCCSP configured to use PKCS11.

Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>
ale-linux pushed a commit that referenced this pull request Oct 5, 2020
Execute the basic query-invoke-query pattern against a solo network with
BCCSP configured to use PKCS11.

Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>
wlahti pushed a commit to wlahti/fabric that referenced this pull request Oct 13, 2020
Execute the basic query-invoke-query pattern against a solo network with
BCCSP configured to use PKCS11.

Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants