Security model
A hotfix system delivers code to every player's device. This page describes what Remendo guarantees, what it relies on, and what it does not protect against.
Authenticity: signed on your side, verified on the device
- Each patch manifest is signed with RSA (3072–8192 bit, PKCS#1 v1.5, SHA-256) using a private key that you generate and keep. Remendo never sees it.
- The matching public keys are pinned in the base player. A device accepts a patch only if its manifest verifies against a pinned key, names the exact build of that player, and every file matches the size and SHA-256 listed in the signed manifest.
- Remendo Cloud checks the same things when you upload, so mistakes show up early. Device-side verification does not depend on it.
What a compromised server could do: withhold patches, or serve an older patch that you signed for the same build. What it cannot do: run code you did not sign. Rotate a pinned key by shipping a new base build.
Activation and rollback
- Downloads are verified, written to a staging area and activated at the next launch, never inside a running game.
- Halting a release sends installs back to the previous release or the shipped code at their next launch.
- On the device, a patch that was loaded at two launches without the game calling
MarkHealthy()is disabled, as is a patch that is refused or fails to load. Disabled patches are not downloaded again.
Encryption is not access control
Remendo can encrypt patched code and metadata to make casual inspection harder. Anything a device can run, a determined attacker on that device can recover. Protect your signing keys and your servers; do not put secrets in client code.
Data
- Each install creates a random install id. It is not derived from the device, is sent only to choose which release an install receives, and is not stored by Remendo Cloud.
- Devices report aggregate events per release: downloaded, applied, rejected, load-failed, local-rollback. No device identifiers, no player data.
- Admin tokens are stored only as hashes. Every upload and release change is written to an audit log.
Reporting a vulnerability
Write to [email protected]. Please give us a reasonable time to fix an issue before disclosing it.