Security & trust
Why Meshanics uses TUF
TLS protects a connection to a server. A file signature proves that one key signed bytes. A secure update system must also decide which version a device may install, whether metadata is fresh, how trust rotates, and what happens when an online key or repository is compromised.
The Update Framework defines that decision system. A Meshanics device starts with a tenant root pinned during enrollment. Before activation it verifies the role chain, signatures, versions, expiry, target path, length and digest.
What this changes
- A registry, CDN, gateway or network path cannot substitute different bytes.
- Previously valid metadata cannot silently move a device back to an older version when version checks reject it.
- Expiring timestamp metadata bounds how long a repository can replay a frozen view of available updates.
- Root authority can rotate delegated keys without granting that authority to the online publishing role.
TUF proves authorization and integrity. It does not prove that the authorized software is safe or healthy. Meshanics therefore keeps vulnerability admission, device health and rollout halt rules as separate controls.