Program Security

Previous Top Next

Tips for increasing your application security



This section is useful for developers who want to:

·	Protect applications against hacking, cracking, and reverse engineering

The number and sophistication of hobby and professional hackers on the Internet has quickly grown over recent years. With the proliferation of discussion boards, peer-to-peer networks, and advanced hacking tools, software developers must go to further lengths to safe-guard their software.

·	Protect from unwanted program modifications

·	Protect against Intellectual Property theft

·	Protect against unknown possible IP lawsuits for copyright and patent issues

With hundreds of millions of patents and copyrights granted each year, it has become nearly impossible to ensure that software products do not violate any patents or copyrights. Using Thinstall aids a lawyer of legal protection by making the burden of proof much more difficult.

Visit our Restricted Discussion board for sensitive information
Because we don't want sensetive information available to potential crackers, please visit the restricted discussion board which is available only to licensed customers for tips on improving your program security.


Thinstall Security Features:

EXE Visibility: If your EXE does not need to perform integrity checks, you should enable this option. This option cannot be used with .NET applications because .NET performs intergrity checks.

Memory Dump Protection: This feature prevents hackers from reconstructing your EXE using tools like ProcDump. This feature can be used with most applications, however it will not work with .NET applications unless "Link .NET Framework" is used. This feature is compatiable with .NET Framework 1.0 and 1.1, but not 2.0.

Anti-debugger Protection: These features will prevent hackers from attaching debuggers to your program, and refuse to run while kernel level debuggers are enabled.

Anti-virus obfuscation: This feature is automatically enable for all EXEs. This feature helps to prevent false positives where anti-viruses companies might mistakenly create a virus definition rule that matches your EXE.


Also see:

WhitePapers -> Software Protection: Preventing memory modifications