Hi Mitchell,
Thanks for your post!
Can you tell me which type of Exe do you want to sign? If you want to sign
..Net assembly, I recommend you use Strong Name technology to get this done.
Strong Name is a build-in security feature for protecting .Net assemblies,
and after signing with Strong Name, CLR will help you to verify the
assembly at loading time. Please refer to the articles below for more
information:
"Cracking .NET Assemblies"
http://www.grimes.demon.co.uk/workshops/fusionWSCrackOne.htm
"Security Briefs: Strong Names and Security in the .NET Framework"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/ht
ml/strongNames.asp
If you want to sign a normal PE file, you can leverage signcode.exe to get
this done, it is shipped with Platform SDK.
Below are two articles that describe how to use it to sign a file:
"Digital Signing for ActiveX Components"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon98/htm
l/vbconunderstandingdigitalsigning.asp
"Signing Files and Checking Signatures"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/cr
yptotools_6cdv.asp
In .Net, you can use System.Diagnostics.Process class to invoke
signcode.exe with command line programmatically.
Hope this helps!
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.