.net - Do I need to publish the public key from .snk file? -


From the description of the sn.exe utility and I see that a copy of the public key is added to each assembly signed with The strong name is enough to verify that the assembly binary has not been changed.

But how does it verify that the given assembly was actually signed with some keypayers and compiled by a company? Anyone can produce their kitpair, produce some assemblies and sign it with their keypier. Do I need to publish the public key so that people who want to verify the assembly origin can compare the public key? If so, what is the best way to do this?

No, you do not need to publish your public key outside the assembly, since it's customer's application In the form of a token with the reference is washed and stored:

  AssemblyName, Version = 1.0.0.0, Culture = Neutral, PublicKeyToken = bcd6707151635d07 " < / Pre> 

provides a way to ensure that all future versions of the assembly are against the same key pair And therefore by the same publisher.

How prevents another source from pretending to be this information, then you can find me in my other answer. / P>


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -