Eziriz.Reactor.LicenseGenerator 7.7.1

.NET Reactor License Generator

Generate .NET Reactor license files programmatically on a trusted server or administrator workstation. This package is the automation counterpart to the License Manager in .NET Reactor.

Security: Do not ship this package, an .nrproj file, a master key, or signing credentials with an end-user application. License generation belongs on infrastructure you control.

Supported targets

The public LicenseGenerator type is in the global namespace in both assemblies.

Install

dotnet add package Eziriz.Reactor.LicenseGenerator --version 7.7.1

Create a license file

Use the same saved .nrproj project and master key that were used to protect the application:

var generator = new LicenseGenerator("MyApplication.nrproj");

// This example creates a license that is not tied to one computer.
generator.Hardware_Enabled = false;

generator.CreateLicenseFile("MyApplication.license");

For a hardware-locked license, set Hardware_Enabled to true and assign the complete hardware ID to HardwareID before creating the file.

You can also load a master key separately:

var generator = new LicenseGenerator();
generator.LoadMasterKeyFromFile("MyApplication.mkey");
generator.CreateLicenseFile("MyApplication.license");

The master key must match the key embedded when the application was protected. A license created with another master key will not be accepted.

External signing with a KMS or HSM

Version 7.7.1 can keep the RSA private key inside a KMS or HSM. Provision a public-only master key once, store it, and reuse it:

string masterKey = LicenseGenerator.CreatePublicOnlyMasterKeyFromPEM(
    File.ReadAllText("license-signing-public.pem"));

File.WriteAllText("MyApplication-public.mkey", masterKey);

The provisioning methods accept:

• CreatePublicOnlyMasterKeyFromDER(byte[]): X.509 SubjectPublicKeyInfo or PKCS#1 RSAPublicKey
• CreatePublicOnlyMasterKeyFromPEM(string): PUBLIC KEY or RSA PUBLIC KEY
• CreatePublicOnlyMasterKeyFromXML(string): public <RSAKeyValue> containing only Modulus and Exponent

RSA keys must be at least 3072 bits. Each provisioning call creates a new random 256-bit license-payload key, so call it only once for a master key and persist the result. Private PEM/XML keys are not accepted by this provisioning API.

Load the public-only master key and send the supplied digest to your signing service:

var generator = new LicenseGenerator();
generator.LoadMasterKeyFromFile("MyApplication-public.mkey");

byte[] license = await generator.CreateLicenseFileAsync(async request =>
{
    // For RSA-3072 with the .NET Standard build:
    // request.HashAlgorithmName == HashAlgorithmName.SHA256
    // request.SignaturePadding  == RSASignaturePadding.Pkcs1
    return await SignDigestWithKmsOrHsmAsync(
        request.Digest,
        request.HashAlgorithmName,
        request.SignaturePadding);
});

File.WriteAllBytes("MyApplication.license", license);

SignDigestWithKmsOrHsmAsync represents your provider-specific integration. The callback must return a PKCS#1 v1.5 signature over request.Digest; it must not hash the digest again. The library verifies the returned signature locally before it creates the license.

In the .NET Framework 4.0 build, the request intentionally uses strings because the BCL types were introduced later:

• HashAlgorithmName: for example, "SHA256"
• SignaturePadding: "PKCS#1 v1.5"

Runtime license checks

This package creates license files. To read the license status or obtain a hardware ID from a protected application, use the Eziriz.Reactor.Licensing package (License.dll) instead.

Documentation

• Create license files with .NET Reactor
• .NET Reactor license system
• .NET Reactor website

License

This package is licensed under the MIT License. You may use, copy, modify, distribute, sublicense, or sell copies, provided that the MIT copyright and license notice are retained.