PKCS#12 File to Sign Assemblies?

[localhost]

I have an individual PKCS#12 file. Can I use it to sign assemblies
instead of using "sn -k" ?

Thanks.

[Yan-Hong Huang[MSFT]]

Hi,

sn.exe uses RSA public/private keypairs specified as either a snk file
(which is simply a CryptoAPI PRIVATEKEYBLOB format) or you can also specify
a CryptoAPI keycontainer name in your source code (or in the VS.NET
AssemblyInfo.cs file) viz:
[assembly:AssemblyKeyNameAttribute("anyCSPkeycontai ner")]

You can use the private key associated with any issued/installed X509
Certificate by specifying the corresponding keycontainer for the cert. If
you do this, you might have to specify the CurrentUser store using:
sn -m n
(sn looks for Machine keycontainer names only).

For whether it is possible to use an existing PKCS#12 file to sign an
assembly, I will contact our specialiast on it to see if it could be done
and reply here as soon as pobbile. If you have any more concerns on it,
please feel free to post here.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C [url]www.microsoft.com/security[/url]
This posting is provided "AS IS" with no warranties, and confers no rights.

[Yan-Hong Huang[MSFT]]

Hello,

Thanks for your patient. I have got the answer of this question. :)

For Signing:

You have two alternatives to sign executables using PKCS #12 (PFX).

Manual Process:

1. Manually import the PFX file into My or Personal "Current User"
Certificate
Store using mmc.exe.
2. Run signcode.exe -cn MyTestCodeSign -r currentUser -s my app.exe
Where MyTestCodeSign is the common name of the certificate
3. Delete the Certificate and the private key.

Programmatically using CAPICOM:

1. Signer.Load --> Loads a signing certificate from a specified PFX file.
2. SignedCode.Sign --> The Sign method creates an Authenticode digital
signature and signs the executable file specified in the
SignedCode.FileName property.
3. Signer.Certificate.PrivateKey.Delete().

Hope that helps.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C [url]www.microsoft.com/security[/url]
This posting is provided "AS IS" with no warranties, and confers no rights.