Topic 9 – Audience
Objective
Know and understand the methods that software producers employ to prevent software copyright legislation being broken.
Why Protect Software?
- Software is intellectual property and is protected by copyright law.
- Unauthorised copying or distribution can lead to financial loss for developers.
- Protection encourages investment in research, development and innovation.
Methods Used by Software Producers
1. Legal Measures
- End‑User Licence Agreements (EULAs) – contracts that define how the software may be used.
- Copyright notices – statements such as “© 2025 Company Name. All rights reserved.”
- Enforcement actions – legal proceedings against individuals or organisations that infringe.
2. Technical Protection Measures (TPM)
- Digital Rights Management (DRM) – controls access and usage through encryption and licence checks.
- Product activation – requires a unique key to be validated online before the software becomes fully functional.
- Serial numbers / licence keys – alphanumeric codes that must be entered during installation.
- Hardware dongles – physical devices that must be attached to the computer for the software to run.
- Obfuscation – makes the source or binary code difficult to read or reverse‑engineer.
- Watermarking – embeds hidden identifiers in the software to trace unauthorised copies.
3. Operational Controls
- Online verification – periodic checks with a server to confirm licence validity.
- Automatic updates – ensure users run the latest, authorised version and can disable cracked versions.
- Usage monitoring – logs usage patterns to detect abnormal activity that may indicate piracy.
4. Educational & Awareness Strategies
- Campaigns that explain the impact of piracy on jobs and the economy.
- Providing clear information on legal alternatives (e.g., free trials, freemium models).
Comparison of Protection Methods
| Method | How It Works | Advantages | Disadvantages |
|---|
| EULA | Legal contract presented at installation. | Clear user obligations; easy to enforce legally. | Relies on user reading and agreeing; may be ignored. |
| DRM | Encryption and licence server checks control access. | Strong technical barrier; can limit distribution. | Can inconvenience legitimate users; may be cracked. |
| Product Activation | Unique key verified online before full functionality. | Prevents mass distribution of unauthorised copies. | Requires internet connection; activation servers can fail. |
| Hardware Dongle | Physical device must be present for software to run. | Very difficult to duplicate; ties licence to hardware. | Costly to produce; can be lost or damaged. |
| Obfuscation | Code is transformed to hide logic and structure. | Raises the skill level needed to reverse‑engineer. | Does not stop copying; only slows it. |
| Watermarking | Hidden identifiers embedded in code or files. | Helps trace source of illegal copies. | May be removed by skilled crackers. |
Typical DRM Workflow (Suggested Diagram)
Suggested diagram: Flowchart showing user request → licence key entry → online verification → decryption of software → usage monitoring.
Key Points to Remember
- Software producers use a combination of legal, technical and operational methods to protect their products.
- Each method has strengths and weaknesses; a layered approach is most effective.
- Understanding these methods helps users comply with copyright legislation and recognise legitimate software.