At present, the default behaviour of cargo‑wdk is to automatically generate a self‑signed test certificate for signing operations, which can be used during the local development and test cycle. If a user wishes to supply their own certificate for signing, cargo‑wdk is currently restricted to accepting certificates with the subject name WDRLocalTestCert and located under WDRTestCertStore, and it throws the following error even when the user’s certificate is installed under WDRTestCertStore:
INFO Signing test_driver using signtool
SignTool Error: No certificates were found that met all the given criteria
To address this limitation, we need to provide a way for cargo‑wdk to accept a custom certificate from a file path or to pick a certificate with a user‑supplied subject name from a chosen store, and allow that certificate to be used for signing.
Related Reference
There is already a separate issue to support customization for rust-driver-makefile.toml #92
At present, the default behaviour of cargo‑wdk is to automatically generate a self‑signed test certificate for signing operations, which can be used during the local development and test cycle. If a user wishes to supply their own certificate for signing, cargo‑wdk is currently restricted to accepting certificates with the subject name WDRLocalTestCert and located under WDRTestCertStore, and it throws the following error even when the user’s certificate is installed under WDRTestCertStore:
To address this limitation, we need to provide a way for cargo‑wdk to accept a custom certificate from a file path or to pick a certificate with a user‑supplied subject name from a chosen store, and allow that certificate to be used for signing.
Related Reference
There is already a separate issue to support customization for rust-driver-makefile.toml #92