Open maxbeckmann opened 5 years ago
x509 for DPS is too complex and highly depend on hw and underlying driver, not sure I can help you but will take time to investigate your case.
This issue has no recent activities, please take a look and provide updates for it.
This issue has no recent activities, please take a look and provide updates for it.
This issue has been automatically marked as stale because it has no recent activities. It will be closed if no further activity occurs within 3 days. Thank you for your contributions.
Hey team,
I am about to implement a custom HSM interface for evaluation purposes. As a first step, my goal was to use a hardcoded certificate. To do this I attempted to follow the instructions at Implementing A Custom HSM from the Azure C SDK repo and implemented a custom DPS client:
As you might guess, this did not work - though the client is trying to connect to the Azure DPS Server. I was able to narrow down the problem to the TLS handshake. It appears the DPS server is aborting the connection after receiving the
certificate verify
. I am now wondering: Why does this happen? Performing the TLS handshake manually was successfull using the following command:Do you have any further suggestion where I might continue my investigations? Do you spot any obvious missconfigurations?
This is the section of my
custom_hsm_data.c
, where the CERTIFICATE variable is set with the contents of new-device.key.pem. The private key is formatted likewise.Thanks! Max