Skip to content

ArmouryDaemon 1.1.5

Choose a tag to compare

@github-actions github-actions released this 22 Oct 07:47
· 125 commits to main since this release

The pack script's host API is scoped by capability. A pack declares the capabilities it wants - "capabilities": ["files"] - and the daemon grants only those: the sandbox keeps one engine per capability set and registers only the granted functions on it, so a call to a function of a capability that was not granted fails as an unknown function. The denial is structural rather than a check a call site could forget, it names the missing capability and what the pack asked for, and it lands in the pack's log. The field is additive and defaults to every capability, so the shipped packs keep working unchanged. The host functions also report what they changed: audio_mute names every session of the process and the state it was in before the call, and it never unmutes a session the user had muted themselves.

The catalogue and the cover art are validated against the Windows certificate store. The catalogue fetch used Mozilla's bundled roots, so it failed on any machine with a corporate CA or with TLS interception, and the cover art was left with the same bug in a second place. Both go through one client now, built once, with the platform verifier: they share its root store and its connection pool, and no client is built for a request any more. The Mozilla bundle leaves the binary with it, and the client refuses the bundled roots instead of falling back to them.

A change of the cooldown re-times the window that is running. The window keeps its start and takes the new length, so it ends at start + cooldown, and the change it is holding lands at the new expiry. Before, the setting changed only the length of future windows: the window in flight ended at the old expiry, the change it was holding landed in that gap, and the game that was starting again then sat held inside the new window with the packs off.

What else changed

  • The dashboard names the app the cooling-down window belongs to, and says that a change is waiting behind the window while one is.
  • The release carries the executable and its hash sidecar, and nothing else. There is no zip and no scripts in it: the executable installs itself, and the scripted install lives in the deploy folder of the repository.

The pack format is unchanged, and the three shipped packs are unchanged.