/ Program Files / Microsoft Visual Studio .NET 2003 / SDK / V1.1 / BIN has a certificate and signature related tools 1. Makecert.exe --- Certificate Creation Tool 2. CERT2SPC.EXE --- Hair Certificate Test Tool 3. Signcode.exe --- File Signature Tools Establishs your own root certificate: makecert -sk mypk -ss myname -n "cn = luo31 studio" -R c: /luo31.cer SK- Represents key container position of the subject, SS - The subject's certificate storage name, N-certificate issuance object, R-certificate storage location; if you need to export private key files, please do not use SK, change it to S, EG: makecert -ss myname -n "cn = luo31 work Room "- SV C: /LUO31.PVK -R C: /LUO31.CER Establishing a self-certification authorization sub-certificate: makecert -sk" mypk "-is myname -n" cn = luo31 "- $ Commercial -ic C: /luo31.cer c: /31.cer SK- Represents the key container position of the subject, IS-issuer's certificate storage name, N-certificate issuer, IC-issuer's certificate storage location, - $ - authorization scope ( Used for code signing); use CERT2SPC to generate SPC issuer certificates (optional): CERT2SPC C: /31.CER C: / 31.SPC Using Signcode for your program, library or CAB package: Double click Signcode, or control Type SignCode and will start the signing wizard without parameters. In the third step, select "Custom Option", the fourth step Select "From File Select" Select 31.SPC or 31.CER, fifth step Select "private key in CSP", select us in the key container MYPK, other steps will be default, if you want to add a timestamp, type: (free timestamp certification) http://timestamp.verign.com/scripts/timstamp.dll; after completion, observe you Signed file properties, you should have added a digital signature item
