One of important characteristics of commercial software is ability to trust the software manufacturer by validating authenticity of the software components. Such functionality can be achieved by digital signing of the released code. Another feature usually implemented at the final stage of the development cycle is code obfuscation which is protecting compiled code from unauthorized disassembly. This document describes three security measures / protection levels that should be implemented as last steps of the release build: code obfuscation, .NET strong name signing and Authenticode signing.
Source: Securing .NET Release Build
CodeProject: Securing .NET Release Build
Similar posts
- Introduction to CQRS — tweetmeme_url = 'http://jesuswasrasta.com/development/int...
- Some practices to write better C#/.NE... — tweetmeme_url = 'http://jesuswasrasta.com/development/som...
- Convert VS2010 .sln back to VS2008 — tweetmeme_url = 'http://jesuswasrasta.com/development/con...
- Smart Continuous Test-Runner For .NET — tweetmeme_url = 'http://jesuswasrasta.com/development/sma...
- Good Exception Management Rules of Th... — tweetmeme_url = 'http://jesuswasrasta.com/development/goo...

