Skip to content

ArmouryDaemon 1.2.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 07:19
· 51 commits to main since this release

Helpers are catalogued now, and installed like packs. A catalogue entry may name a helper
module
: an archive plus the executable inside it (entry). The catalogue window is the
Modules window, and packs, modes and helpers render in one list - a helper's state comes
off its own module.json record on disk, not off the daemon's pack folder. Its row carries a
real Download button: clicking it downloads the archive on a worker of its own, verifies it
against the manifest, and hands the daemon an InstallHelper request naming the id, the
version, the executable's path inside the archive, the SHA-256 and the size. The daemon is the
last to read the file: it must sit in temp under the download's name shape, its bytes are
re-checked against the SHA-256 they were named with, and only then is it extracted into
modules/<id>/ - the folder and its parent carry an Administrators + SYSTEM full, user read +
execute lock - the layout recorded in the folder's module.json, and the temp archive removed
whatever the answer is. A helper joins no pack or mode worker; --module-list lists every
installed pack, mode and helper from disk.

The manifest those entries come from is minisign-signed. The fetch reads index.json,
then index.json.minisig, and verifies the signature against a keyring baked into the binary
before parsing anything: an unsigned or badly signed manifest refuses by name, and nothing
is installed or listed. The manifest also reaches schema 2 - entries under modules, an
entry naming its kind - and the daemon still reads a schema-1 manifest's packs key for this
release, so an old manifest keeps loading while one that carries both keys refuses. The packs
repo has not published its signed manifest yet, so the fetch of the live catalogue refuses by
name until that flip; the shipped packs in packs/ and the local probes need no flip.

The killswitch is configurable. One field, killswitch_enabled (default on), is the
switch and the "is the module installed" flag: while it is off the End key and the tray
toggle are logged no-ops and the tray item reads "Killswitch off in config";
{"type":"set_killswitch"} carries the decision over the pipe; the state survives a restart;
and turning the switch off releases an engaged killswitch first - windows back, audio back,
tray icon back. A status from an older daemon still means on. And modes stopped holding the
queue
: mode packs get a worker and channel of their own, and a mode whose steps take seconds
no longer delays the apply or the revert of a pack beside it; the running state and the
journal read as they always did, and nothing changes for a pack - kind defaults to "pack",
and a mode still arrives only through the ordinary tracked-app trigger.

The executable carries its own C runtime: the MSVC build links the CRT statically, so it
imports no VCRUNTIME140.dll and starts on a stripped image where the VC redistributable was
never installed.

What else changed

  • Quitting releases an engaged killswitch. The quit path used to revert the packs and leave
    idle mode while the killswitch rode past both: its hidden windows die with the process, but
    its mutes live on the audio devices - the machine could stay hidden and silent until the
    daemon started again. The killswitch is released between the revert and the exit now.
  • A failed download leaves the row offering its button. The failure line the Modules window
    paints could extend wider than the list without a width cap, pushing the rows' right-aligned
    buttons past the window edge, where they clipped away and came back only at restart. The
    line wraps like the notes under the rows now.

The pack format is unchanged, and the three shipped packs are the bytes they were -
Wallpaper Engine 1.4.0, G-Helper 1.3.1 and Rainmeter 1.5.0.