Software protection dongle DGL-1

Typical usage scenario #

Key generation: developer creates two types of cryptographic keys: a private key for their application and a private key for a series of dongles. These keys are unique and provide the basis for secure data exchange.

Presence and authenticity verification: upon launch, the application uses the dongle's public key to verify its presence and authenticity. This ensures that the software only works with an authorized DGL-1 device, preventing unauthorized use.

Permissions retrieval and verification: after successful verification, the application reads a special file (this can be XML or JSON) from the dongle that contains information about the user's permissions. This file is signed with the application's private key, ensuring its integrity. The application verifies the signature and applies the permissions defined in the file, providing granular control over functionality.

By using an asymmetric encryption algorithm, the DGL-1 dongle opens up additional possibilities for protecting your software. Some critical parts of the application, such as resources or individual modules, can be encrypted with a public key at the build stage. At runtime, when the application needs to access this protected data, it can use the dongle's functions to securely decrypt it. This provides a reliable level of protection, since even if an attacker obtains a copy of the application, he will not be able to access the encrypted components without an authorized dongle.

This process provides multi-layered protection: dongle authentication, integrity of permission data, and access control at the application level. DGL-1 allows developers to effectively protect their applications from piracy and unauthorized use, while providing flexibility in managing licenses and functionality.