.net - Using the Public Key of Signed Assembly as a Security Measure -
I am writing a security measure with an application that I am writing where I have a security DLL . If this assembly is present, then I check the byte array which comes back when it receives the public key, and compares my application.
Is there sufficient security to ensure that no one has amended my assembly or will have to return the public key to its own DLL at the right place?
I have seen what obobscoters do and they resign my assembly, but are they actually using SNK or are they using the internal assembly and reuse it?
If you If the SNC file is used to keep the assembly safe, then no public key should be able to create a new security dell.
A cryptographic key pair is required to sign the assembly with a strong name. The private key of this pair is used to sign the assembly. If a security assembly was to be modified, it will need to be re-signed, for which the original snack file will be required. If a different snack file is used, then the assembly will have a different public key.
If you add the reference to the security dll, the runtime will ensure that the correct assembly is used while loading it. If an assembly meets with the same name and version, but with a different strong name, then you will get an error because this framework will be classified as a separate assembly from the one originally referred to.
For more information.
Comments
Post a Comment