Safeguarding the Integrity of Expiration Algorithms in Trial Versions of Software Programs.

1. Safeguarding the Integrity of Expiration Algorithms in Trial Versions of Software Programs. Kevin M. Arvin CS 689

2. ProblemStatement In order to expose their products to a wider audience, many commercial and independent software developers release time limited trial versions of their software. While this practice can increase sales, a number of individuals have developed methods to circumvent the trial versions’ protection algorithms called “cracks”. The cracks are being widely distributed on the Internet allowing anyone to obtain the software without compensation to the developers.

3. Background • Try before buy approach introduced with shareware • Commercial Programs have adopted the approach • Expiration algorithms are usually not effective • Cracks are readily available on the Internet

4. Research Objectives A number of individuals who “crack” programs publish tutorials on the Internet that explain how they do it. Our goal is to use these pages to develop methods to protect the evaluation versions’ trial periods.

5. Benefits of the Research In this project, we will examine those web pages and attempt to counter their methods one by one. If successful, we should be able to produce a set of program design recommendations and algorithms that will make software uncrackable. • Programmers would receive the revenue they deserve for their work. • Increased developer income should lead to better quality software. • Increased sales will result in lower prices for consumers. • Increased sales should result in better technical support. • Increased profits will result in a larger number of programs being produced. • Porting applications to less popular platforms may become feasible. • Will help start-ups with limited resources be successful. • Should lead to increased competition in the software industry.

6. Research Methodology Data-Gathering Phase • The project will recruit participants from the following sources: • Professional developers. • University faculty. • Graduate level computer science students. • Undergraduate computer science students. Participants will examine the cracking tutorials, catalog all the methods used, and devise new methods to counter each one.

7. Research Methodology Testing Phase A test program will be created.

8. Research Methodology Areas Excluded from Research • Issues related to specific development environments. • Issues related to specific programming languages. • Issues related to operating systems other than MS Windows. • Hardware solutions. • Solutions that require proprietary technology. • Platforms other than the IBM compatible PC. • Alternate distribution and registration strategies.

9. Future Areas of Research Any or all of the excluded areas are suitable for further research. If the research is successful, someone will eventually find a way to defeat its recommendations. At that time the project will need to be repeated.

10. Deliverables • The final product(s) of the research cannot be determined at this time. However, the project will probably produce the following: • Source Code • Program design recommendations

11. Project Schedule

12. Questions ? Ask them now, Or send them to: kvnrvn@dmrtc.net