DevEntitle

Signing releases

Every release on DevEntitle is signed on your own machine with an Ed25519 key. DevEntitle never sees your private key. It checks every upload with your public key, and your product checks the download again before installing it. So even if someone took over the update server, they still couldn't push a fake update to your buyers.

How it works

  1. Once: create a keypair. Paste the public key into your product on DevEntitle (Edit product → Release signing) and ship it inside your product. Keep the secret key offline.
  2. Each release: build <product>-<version>.zip, then sign it. Signing writes a small .json manifest next to the zip.
  3. Upload the zip and the manifest in DevEntitle (Releases → Upload release). The upload is refused if the hash or the signature doesn't match.
  4. Publish it. Licences that are entitled to it get a download link from /api/v1/updates. The link expires after 30 minutes, and the zip is served exactly as you uploaded it.

The Release Kit

A free single-file tool that works without installing anything. Use whichever language your build machine has; both produce the same keys, manifests and signatures. Neither sends anything anywhere.

1. Create a keypair (once)

php deventitle-release.php keygen
# or
node deventitle-release.mjs keygen

Store the secret key in a password manager and in your build machine's environment only. Never commit it, put it on a server or upload it to DevEntitle. If you lose it, create a new keypair, put the new public key on the product, and ship a release containing the new public key (signed with the old key, if you still have it, so existing copies can install it).

2. Sign a release

export DEVENTITLE_SIGNING_KEY="<secret key>"
php deventitle-release.php sign acme-crm-1.2.0.zip
# → acme-crm-1.2.0.json

The product slug and version are read from the file name <slug>-<version>.zip, or passed with --product= and --version=. You can use --key-file=<path> instead of the environment variable. The key is never accepted on the command line, so it doesn't end up in your shell history.

3. Check it (optional)

php deventitle-release.php verify acme-crm-1.2.0.zip --public-key="<public key>"

The manifest

{
    "product": "acme-crm",
    "version": "1.2.0",
    "sha256": "<hex SHA-256 of the zip>",
    "size": 36168558,
    "signature": "<base64 Ed25519 signature>",
    "built_at": "2026-11-01T09:30:00Z"
}

The signature is Ed25519 over the UTF-8 text <product>|<version>|<sha256>, with the SHA-256 in lower-case hex. product is optional. Keys are base64: 32 bytes public, 64 bytes secret (the libsodium format). HUBCITY CRM's php artisan wise:release writes the same manifest, so its builds upload as they are.

Versions look like 1.2.0, 1.2.0.4 or 2.0.0-beta.1. A version can be uploaded only once per product. If something was wrong, upload a new version; installed copies may already have checked the old one.

Checking updates in your product

When /api/v1/updates returns a latest release with a download_url, download the zip, then check both the hash and the signature with the public key that is built into your product, before installing anything:

$sha = hash_file('sha256', $zipPath);
$ok = hash_equals(strtolower($latest['sha256']), $sha)
    && sodium_crypto_sign_verify_detached(
        base64_decode($latest['signature']),
        'acme-crm|'.$latest['version'].'|'.$sha,
        base64_decode(ACME_RELEASE_PUBLIC_KEY)
    );

if (! $ok) {
    // Refuse: the file was changed or not signed by you.
}

When the licence isn't entitled to the newest version (for example, support ended before it came out), latest still has the version, notes and a message, but no download_url or signature. Show the message, and keep the installed version working: a licence on DevEntitle unlocks updates, downloads and support, and must never switch features off.

Channels

Each release is stable or beta. Licences on the stable channel are offered stable releases only. Licences on the beta channel (set on the licence type, or per licence) are offered whichever is newer.