Skip to main content
Enigm Link has controlled update workflows for desktop apps and Enigm Link Boot OS. Updates are delivered through the official Enigm Link product flow and are not public manual installation packages. The current production update channel is:
Update delivery is controlled by product eligibility, official USB validation, protected transport requirements, and release verification. Public documentation intentionally describes the trust model, not deployable update-service structure or internal storage details.

​
Overview

Enigm Link updates are designed to be served only under authorized conditions. The update model uses:
  • Official USB validation.
  • VPN-gated update access.
  • Request authentication.
  • Manifest validation.
  • Build allowlisting.
  • Artifact integrity checks.
  • Critical configuration checks.
  • Fail-closed behavior when required security conditions are missing.

​
App Update Flow

The app update flow is conceptually:
  1. The app detects the installed version.
  2. The app requests update eligibility through the controlled product update flow.
  3. The update workflow validates protected state, request authentication, and allowed build state.
  4. The app downloads the authorized package.
  5. The app prepares staging.
  6. The app updates the visible product application content.
  7. The app preserves official USB identity.
  8. The app cleans staging and backup files.
  9. The app relaunches when the update is ready.
Official Enigm Link devices can move from an older authorized app build to a later production build through the controlled updater when eligibility checks pass.

​
App Update Requirements

App updates should:
  • Avoid leaving incomplete platform folders if an update fails.
  • Preserve official USB identity.
  • Hide or clean auxiliary files within host-platform constraints.
  • Keep each platform folder limited to the visible app or executable.
  • Minimize the time between app shutdown and relaunch.
  • Avoid depending on a fixed Windows drive letter.
  • Avoid requiring the user to manually replace product files.

​
Boot OS Update Flow

Boot OS updates should:
  • Validate release metadata.
  • Preserve the visible user-facing app boundary.
  • Update Boot OS release material where required.
  • Verify checksums and final payload integrity.
  • Preserve official USB identity.
  • Maintain PC UEFI and Mac Intel compatibility.
  • Return cleanly when no Boot OS update is available.
Boot OS updates must not be documented as supporting Apple Silicon Boot OS in the current amd64 release. Boot OS updates are product-managed updates. Users should not manually replace boot material, internal runtime material, or official USB identity data.

​
Update Service Security

The controlled update system is designed to:
  • Keep update distribution separate from public manual download behavior.
  • Require traffic through the authorized VPN path for protected update access.
  • Validate request authentication.
  • Validate allowed source and build state.
  • Validate release manifests.
  • Fail closed if critical security configuration is missing.
Public update documentation remains intentionally high level. It does not provide USB provisioning, device manufacturing, repartitioning, manual Boot OS installation, bypass instructions, private service structure, or deployable update-service details.

​
Relationship With Enigm Command

Enigm Command provides the lifecycle and policy context for Enigm Link updates. Command-side context can include:
  • Product entitlement.
  • Official USB registration.
  • Device lifecycle state.
  • Support review.
  • Update eligibility.
  • Security status visibility.
Update eligibility does not provide access to protected user communications. See Platform Limitations.