What configs need to be set to enable certificate based provisioning?
Doc states configs for input and output but not for certificate based provisioning
What configs need to be set to enable certificate based provisioning?
Doc states configs for input and output but not for certificate based provisioning
Hi Utkarsh,
Unfortunately, Certificate-based Provisioning isn't supported yet. This is as of the time of writing, with the newest nRF Connect SDK version being v2.7.0.
If you have a great interest in this, please share it with your local Nordic sales representative.
Hieu
It is possible I think in zephyr. Is certificate-based provisioning a subset of static OOB provisioning? How to enable it? There are two variables *public_key_be; *private_key_be; that need to be passed but as I have generated a private key using PSA crypto I am not able to pass the actual private key to this variable as I only have the key handler of private key
It is possible I think in zephyr. Is certificate-based provisioning a subset of static OOB provisioning? How to enable it? There are two variables *public_key_be; *private_key_be; that need to be passed but as I have generated a private key using PSA crypto I am not able to pass the actual private key to this variable as I only have the key handler of private key
No, Certificate-based Provisioning is not a subset of static OOB provisioning. See this document: https://www.bluetooth.com/bluetooth-certificate-based-provisioning-a-technical-overview/.
Thank you
No problem. If you don't have any questions on this topic anymore, feel free to close it at your convenience.