Why do I want to protect my Java or .NET application from decompilation?
Stamping out vulnerabilities is the best thing – and doing so earlier is better than later – but no one can guarantee zero vulnerabilities. (If we could we would not see the continuous stream of patches and alerts from every software and system supplier under the sun.) At least as important are the issues surrounding IP theft and piracy. These issues persist even with “vulnerability-free code.” Last, there are a number of scenarios where a tampered application plays a pivotal role (piracy, spoofing, malicious attacks, etc.) even if an application is released with no exploitable vulnerabilities. A tampered application may have some vulnerabilities introduced “post-production.” The only defense in this last case is to “detect”, “defend” and “notify” when tampered applications are run. This is uniquely offered within Dotfuscator and DashO.
Related Questions
- Why does my application sometimes receive a NativeSeqFile error when using JRIO and the Remote Method Invocation (RMI) - Java Remote Method Protocol (JRMP) to access MVS datasets?
- Why do I want to protect my Java or .NET application from decompilation?
- What Type of Data Can an Application Access Through the OLAP Java API?
