RE: protecting .NET assemblies against hackers
From: Shen (Shen_at_discussions.microsoft.com)
Date: 10/27/04
- Next message: SLY: "Re: Mixing authentication type flags & By design Bug from MS ?"
- Previous message: DT: "Re: Security Policy Confusion..."
- In reply to: Nate A: "protecting .NET assemblies against hackers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 27 Oct 2004 07:29:03 -0700
Hi,
For assembly with encryption/decryption code, I would:
1) Delay sign the assembly during development.
2) Use code access securty so that only certain user/role can run the
assembly.
3) Obfuscate the DLL after development.
4) Sign the assembly with strong name tool(sn.exe) so that no one can modify
the assembly.
Hope this will help you.
Weidong Shen
- Next message: SLY: "Re: Mixing authentication type flags & By design Bug from MS ?"
- Previous message: DT: "Re: Security Policy Confusion..."
- In reply to: Nate A: "protecting .NET assemblies against hackers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
