Software Activation System Using Asymmetric Key Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software activation methods rely heavily on Internet connections, leading to security issues such as unauthorized software usage and inefficiencies in managing activation states, which result in increased customer support inquiries.
Innovation Solution
A secure software activation process using a unique pair of keys for each vendor application, with a public key integrated into the application and a private key stored on a server, employing digital signatures to validate licenses and prevent tampering, along with mechanisms for remote license management and reactivation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Internet connection is required for software activation, then license verification can be performed, but security vulnerabilities and unauthorized usage increase
Solution Approach 1:
The activation system is segmented into client-side components (application, public key) and server-side components (private key, database). This segmentation allows the verification logic to be distributed, with the client performing local validation using the public key and the server maintaining authoritative license state, thereby reducing security vulnerabilities associated with centralized Internet-based activation.
Solution Approach 2:
The public key is embedded in the application during compilation, and license files are pre-signed by the server before distribution. This preliminary action ensures that verification can occur locally without requiring real-time Internet connection, preventing unauthorized usage while maintaining reliable license verification.
2Ease of operation
If fake license files are generated on client machine, then verification can be bypassed, but security is compromised
Solution Approach 1:
The system moves from a single-dimensional client-generated license model to a multi-dimensional model where licenses are cryptographically signed by the server and verified using asymmetric cryptography. This dimensional change in the verification mechanism makes it computationally infeasible to generate fake licenses, as the private key required for signing is securely stored only on the server.
Solution Approach 2:
Cryptographic signatures act as an intermediary between the server and client, providing a trust mechanism that eliminates the need for client-side license generation. The digital signature serves as a verifiable intermediary proof of authenticity, preventing fake license creation while maintaining ease of verification.
3Device complexity
If activation state is not tracked, then system complexity is reduced, but customer support inquiries increase
Solution Approach 1:
The server maintains a database that provides feedback on the activation state of each license. This feedback mechanism tracks whether a license is activated, deactivated, or transferred, enabling automatic enforcement of activation policies and reducing the need for customer support intervention. The feedback loop occurs whenever activation status changes, ensuring accurate tracking without excessive system complexity.
4Ease of operation
If reactivation is allowed without tracking, then ease of operation is improved, but unauthorized usage increases
Solution Approach 1:
The activation system dynamically adjusts license state based on server-side tracking. Reactivation is allowed only when the server determines it complies with the license agreement terms. The system transitions between activated and deactivated states based on verified user actions and policy compliance, preventing unauthorized simultaneous usage while maintaining ease of legitimate reactivation.
Data Source
AI summary
System and method for software activation and further tracking of its states on an end-user computing device (computer) was developed to provide software developers a flexible and secure tool for software distribution and gathering statistics of usage of software activation. The method consists of the following logical steps: (a) obtaining an acquisition confirmation; (b) requesting for a license; (c) issuing and delivering the license to End User, the license being secured with a private key by a server, and the private key is not stored at the client; (d) verification of license on the User's computer; (e) storing the license on the User's computer; (f) periodic tracking of activation state, (g) another action with the User's license, wherein the verifying the license comprises validating, at the client associated with the application, the license received from the server without any modifications, and saving the license to the client.