Menu
I have lot of assemblies inside one folder. Only some of them are marked for delay signing.
Now, I have to sign all those assemblies who have marked for delay signing.
How to identity which assembly is marked for delay signing and which is not?
491
You can run sn -v "path to your assembly" . This will output xxx is a delay-signed or test-signed assembly if the assembly is delay signed. sn -v doesn't show me xxx is a delay-signed or test-signed assembly .
To detect whether the assembly file is signed or not, right click on the file and click the 'Properties' from the context menu. If you see a 'Digital Signatures' tab in the properties window, that means, the file is signed by a digital signature (as shown below).
Delayed signing refers to a technique of partially signing assemblies while they are in the development phase. So, signing an assembly basically certifies that assembly by the manufacturer and prevents tampering and hi-jacking of that assembly.
Signed dll are strongly named. A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a digital signature.
You need to use sn -vf
Verify for strong name signature self consistency. If -vf is specified, force verification even if disabled in the registry.
181
You can run sn -v "path to your assembly". This will output xxx is a delay-signed or test-signed assembly if the assembly is delay signed.
If you prefer to do it in .NET, you may want to use StrongNameSignatureVerificationEx to check the signature (http://blogs.msdn.com/b/shawnfa/archive/2004/06/07/150378.aspx)
[DllImport("mscoree.dll", CharSet = CharSet.Unicode)]
static extern bool StrongNameSignatureVerificationEx(string wszFilePath, bool fForceVerification, ref bool pfWasVerified);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
