Automatically created using vs2005. pfx digital certificates are only valid for one year by default, and both the "issuer" and "issued to" are combinations of the current machine name and current Login User name. In fact, we can create more friendly. pfx digital certificate.
Follow these steps to open the SDK Command Prompt for Microsoft. NET Framework:
1. Create a self-Signed X.509 Certificate (. CER) and A. PVK private key file and use the makecert tool. The command is as follows:
Makecert-r-n "cn = cncxz"-B 01/01/2005-e 01/01/2018-SV myselfname. PVK myselfname. Cer
Set the private key password as prompted (or do not use the password) to generate related files in the current directory.
2. Use X.509 Certificate (. CER) to create a issuer certificate (. SPC) and use the cert2spc tool. The command is as follows:
Cert2spc myselfname. Cer myselfname. SPC
3. Convert from. PVK and. SPC to. pfx. The pvkimprt tool is used. The command is as follows:
Pvkimprt-pfx myselfname. SPC myselfname. PVK
Follow the prompts to export the. pfx certificate. If the private key password is set in step 2, enter verification here.
4. Click "select from file" in the certificate settings of the clickonce list signature of the vs project to browse and find the certificate exported in step 1. pfx certificate. Verify the private key password of the certificate set in step 1.
========================================================== ==========
The makecert tool and cert2spc tool. NET Framework come with the following pvkimprt tool:
Http://download.microsoft.com/download/vba50/Utility/1.0/NT5/EN-US/pvkimprt.exe
Original article: http://www.cnblogs.com/cncxz/archive/2007/03/15/675937.html