However even with the CSP architecture, there are 2 approaches depending on how recent the implementation of the vendor is. When you install the drivers of the smart card, the vendor will provide the necessary libraries that integrate within this framework. Now the only thing you need to do is to use the proper CSP (Crypto Service Provider) for your smart card. Before the BaseCSP and minidriver architecture, you would have needed to use PKCS#11 and write a lot of interop code. What you need to know is that this framework saves you a lot of code and burden to integrate PKI smart cards in a. I'm not going to describe here this framework as you can find a lot of good articles on the WEB that do that. Microsoft Next Generation Smart Card Framework When generation is done, you will be prompted to give passwords. This is going to generate 2 files that we need to use, the smartcert.cer contains only the public key (although it is possible to include the private key) and the smartcard.pfx is a full RSA key pair that is protected by password because the private key is the most sensible part of a certificate. Pvkimprt -pfx smartcert.spc smartcert.pvk In a DOS shell, you'll have to type the following commands after setting the correct path.Ĭopy Code makecert -r -n "CN=CodeProject" -b -e Pvkimprt is an Office utility that can be downloaded from Microsoft WEB here. Makecert and cert2spc are available with Microsoft SDKs and can be found in the " Program Files\Microsoft SDKs\Windows". pvk into the desired PFX file (PKCS#12 format) spc format (Software Publisher Certificate)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |