|03 Sep 2013||#1|
| || |
How to digitally sign a Cryptographic Service Provider (CSP)
We are in the process of developing a Cryptographic Service Provider (CSP) and a Key Storage Provider (KSP) which are implemented as Dynamic-link libraries (.dll). The final product needs to be digitally signed in order for Windows to accept and use our implementations.
I read on MSDN that developers used to send an email to firstname.lastname@example.org and request that Microsoft do the signing. I sent an email to them, requesting more information about the process, but haven't received any feedback in about three months.
I figured an alternative would be to buy a "Code Signing certificate for Microsoft Authenticode" from a trusted CA, such as Symantec, and use that to sign the appropriate files ourselves. Would this be possible? I am just not sure whether it is permitted that security products, such as CSPs and KSPs, can be signed by the developers themselves and whether Microsoft wants to look at the implementations first.
Can anyone shed some light on this?
|My System Specs|
|Similar help and support threads for2: How to digitally sign a Cryptographic Service Provider (CSP)|
|How to debug a Cryptographic Service Provider?||Software|
|How to digitally sign my own .sys file?||Drivers|
|Getting error ' cryptographic service not running '||Browsers & Mail|
|Internet Service Provider||Chillout Room|
|New Scareware Leverages the Layered Service Provider.||Security News|
|digitally sign||System Security|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 03:05 PM.