[
https://issues.apache.org/jira/browse/PROTON-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865535#comment-17865535
]
ASF GitHub Bot commented on PROTON-2594:
----------------------------------------
a3f commented on PR #430:
URL: https://github.com/apache/qpid-proton/pull/430#issuecomment-2225923971
> is there any way of testing this functionality in the CI job? (Rather than
just testing that nothing regressed!)
How about we apply [this
patch](https://github.com/a3f/pkcs11-provider-qpid-proton-bug-reproduction/blob/master/0001-HACK-PROTON-2594-cpp-connect_config_test-adapt-for-t.patch)
and then run the test twice once with PEM files and once with PKCS#11?
> Use of HSM for crypto opterations with the private key of a TLS certificate
> ---------------------------------------------------------------------------
>
> Key: PROTON-2594
> URL: https://issues.apache.org/jira/browse/PROTON-2594
> Project: Qpid Proton
> Issue Type: New Feature
> Components: cpp-binding, proton-c
> Reporter: Franz Hollerer
> Priority: Major
>
> We use a Hardware Security Module with PKCS#11 Interface (to be more
> specific: OP-TEE) as key store. This key store holds the public and private
> key for a TLS certificate for the purpose of client authentication.
> Is there a way to instruct proton-qpid to use the HSM for cryptographic
> operations with the private key?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
