Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I see tool like SN which generates private/public key pair for signing an assembly.
and using AL tool we can assign a strong name to an assembly
And we have also Sign tool which is used for signing the assembly (probably for using with certificates exclusively?).
What is the exact difference between the two?. Is it sign tool have to be used when working with certificates and can it we acheive it SN?. or are they totally different.?
Please help.
Signtool is to do code signing, which provides code integrity check and authentication of the publisher.
Sn is to do strong name. It’s just for .NET assembly. It addresses the unique ID issue.
Both tools can make sure the files have not been tampered with but only code signing (signtool) can assure you who is the publisher of the files.
We can use SignTool.exe to sign and time stamp a file with given pfx, even though the file is a strong named dll.