Home > Articles > Security > General Security and Privacy

  • Print
  • + Share This
This chapter is from the book

1.9 Discussion

There are plenty of reasons to use the techniques you will read about in this book to protect your code, and plenty of reasons not to. In the end, you must weigh the pros and cons to see if using them makes sense in your particular case.

1.9.1 Reasons to Use Software Protection . . .

On the plus side, there are situations where even a short delay in cracking your code will be beneficial. For example, these days computer games often escape into the wild within days or a few weeks of release. Sometimes, as the result of insider attacks, they even escape before they’re released! Since gamers are interested in playing the latest and greatest, the revenue from a new game is typically collected within the first few weeks of its release. Game manufacturers have therefore traditionally been eager to adopt software protection techniques, even those that are sure to be cracked within a very short time.

In situations where you’re selling a particularly high-value program, software protection might also make sense. If every year you sell only a few tens of copies of a software system that costs $100,000 per seat, the loss of even one sale due to piracy could be devastating to your bottom line. In these situations, it’s common to use a combination of hardware techniques (such as dongles) to prevent illegal copying and software techniques (such as obfuscation) to protect the interface between the hardware and the application.

In some situations, you may want to use software protection to prevent individuals from cracking your program, individuals you are unlikely to catch (because they’re far off in another country) or who are legally untouchable (because they have no assets to forfeit). In other cases, you may want to use software protection as an aid in criminal prosecution. It is said that more money is lost to piracy performed by corporations than by individuals. The reason is that corporations often will buy, say, 10 licenses to use a program but will let 50 of their employees use it. These corporations have huge assets, and if you can prove license infringement, you may actually have a chance to use the legal system to force them to abide by the license agreement. Individuals, on the other hand, often crack a program or download a pirated program that they would never have bought legally anyway. The amount of revenue lost to this type of piracy may therefore not be as high as often reported, and going after these types of adversaries is less likely to be profitable.

1.9.2 . . . and Reasons Not To

On the downside, adding software protection to your program can cause problems in terms of cost, performance, a more complex software development cycle, and last but not least, annoyance to your legitimate users.

Costs can increase both during development and distribution. During development, you have the option of purchasing a protection tool, developing one yourself, or applying the protection techniques by hand. Regardless, you will be adding a step and complexity to the development cycle. In several techniques you’ll see in this book (such as fingerprinting and code encryption), every distributed copy of your program will be unique. This means additional headaches during distribution, quality assurance, and when fielding bug reports.

Many of the techniques you’ll see come with significant performance overhead. And when we say “significant” we mean significant. Whether higher levels of protection necessarily incur a more severe performance hit is unknown, but it seems not an unreasonable possibility. In the end, this may require you to make difficult trade-offs: using techniques with low overhead and a low level of protection, using powerful techniques with high overhead but only for the security-sensitive parts of your program, or accepting the high overhead of a powerful protection technique but only selling to users with sufficiently powerful computers.

Many software protection techniques have been cracked not because the attacker necessarily wanted to pirate or reverse engineer the program, but because he wanted to perform what to him seemed like reasonable operations on it. Maybe he wanted to run the program on his laptop as well as his desktop computer, maybe he wanted to make a backup copy of it, maybe he wanted to transfer it from his old machine to his newly bought one, maybe he wanted to run the program without the annoyance of having to enter a password or insert a CD or USB token every time, and so on. Whether or not you, as the software developer, think these are legitimate concerns, and whether or not the software license agreement allows it, the user may well get ticked off enough to feel no qualms about cracking the program.

And that’s not to mention bugs. Many of the techniques you will see in this book are based on code transformations. As such, they’re very similar to the optimizing code transformations you’ll find in sophisticated compilers. And as such, they’re susceptible to the usual menagerie of bugs. As a result, your program that was perfectly functional before protection was added may exhibit erratic behavior afterward, either as a result of a bug in the protection tool itself, or because its code transformations revealed a latent bug in your own code.

1.9.3 So Which Algorithms Should I Use?

So you’ve written your fantastic new program and for whatever reasons you’ve decided that it makes sense to add some sort of software protection to it. You’ve bought this book5 and read it cover to cover in search of the One True Algorithm to implement. Unfortunately, if this was your attitude, you will have been sorely disappointed.

The problems facing software protection research are multitudinous, but it boils down to one central issue: How do you evaluate the effectiveness of an algorithm? Unfortunately, the state of the art is sorely lacking. Ideally, this book would end with a single large table over all the algorithms that lists for each one effort to implement, effort to defeat, parallelizability of attacks, and performance overhead.6 As you may have already guessed, there’s no such table.

Without knowing how many more hours/days/weeks/months your program will remain uncracked if you protect it with the algorithms in this book, how can you know if software protection will make sense in your particular case? And without being able to compare two algorithms to say that one is better than another, how can you pick the right algorithm to use? And how does the field progress when a paper purporting to present a new, improved algorithm can’t substantiate its claims?

Disturbing questions, indeed. In practice, software protection takes a belt-and-suspenders approach to security. You layer protection algorithms until you’ve convinced yourself that your program is secure “enough” while at the same time remaining within performance bounds. If you can afford to, maybe you employ a professional red-team to try to break through the defenses and give you some feel for how long the protection will survive in the wild. But in the end, you have to accept the fact that you’re engaged in a cat-and-mouse game: If crackers deem your program sufficiently crack-worthy, eventually they’ll succeed. This situation may seem depressing, but it is not much different from other areas of life. In the end, all it means is that you will have to monitor the efforts of your adversaries and be prepared to continuously update your defenses.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020