๐ Security
Two low-severity integrity issues reported privately by @HomeRiz
(GHSA-hh8r-m7q2-gxqc), plus a local token-storage fix:
- Icon map downloaded without certificate checks. When
mdi_mapping.json
was missing, the app downloaded the Material Design Icons CSS with TLS
verification turned off, so anyone on the network path could swap in a
different file. It is now downloaded with full certificate and hostname
checks and a 30-second timeout. The impact was limited to which glyph each
icon name shows. Nothing from that file is ever executed. - The updater accepted assets that SHA256SUMS didn't list. If a release
published a SHA256SUMS file with no line for the file being downloaded, the
updater treated that as a pass. It now refuses the update, and SHA256SUMS
covers every asset on the release, including the AppImage and the Windows
installer. The sums file comes from the same release as the update, so this
is a consistency check, not a signature. - The fallback token file could be read by other users on the same
computer. On macOS, and on Linux without a working keyring, your token is
kept in an encrypted file next to Prism's config. That file
and its salt were created world-readable, and the key is derived from
machine identifiers that any local account can read. If another account
on the computer could reach that folder, it could decrypt your token.
Both files are now private to your account, and files left by older
versions are tightened too. If other people have user accounts on your
computer, create a new Home Assistant token and delete the old one. - Prism no longer retries forever after Home Assistant rejects the token.
Withip_ban_enabledon the Home Assistant side, those retries could get
your machine banned. - Raised the minimum dependency versions so installs from source don't pull
in releases with known vulnerabilities - thanks @HomeRiz (#69).
Thank you to @HomeRiz for finding both integrity issues, reporting them
privately, and sending fixes along with a test suite.
โจ New
-
System sensors for Home Assistant (off by default). Two new toggles
under Settings โ Home Assistant:- System health: battery level, charging, disk usage, CPU temperature,
last boot - Presence: idle time, screen locked, microphone in use, camera in use
Sensors your machine can't provide (battery on a desktop, camera state on
macOS) are never registered, so they don't show up as permanently unknown
entities. The Linux collectors are tested. The Windows and macOS ones are
new, so please report anything that looks wrong. - System health: battery level, charging, disk usage, CPU temperature,
-
Per-tile update indicators - a small dot flashes on a tile when Home
Assistant pushes a live update. Off by default under Settings โ Appearance โ
Options โ Update indicators. Thanks @HomeRiz (#65). -
The Nix flake now updates itself on each release - thanks
@niklasthorild (#67, #68).
๐ Fixes
- Python 3.15: running from source on Python 3.15 left every connection to
Home Assistant hanging (an incompatibility in qasync 0.28), and silently
turned off notification action buttons, the Wayland global shortcut and
location on Linux (dbus-next uses a function 3.15 removed). Prism now works
around both. Running from source requires Python 3.11 or newer. - The alarm overlay sent a disarm when you tapped an arm button after a
disarm. - The entity picker chose the wrong entity when two entities had the same
friendly name. - Scenes and buttons that had never been triggered (still
unknown) could not
be triggered, including 3D printer pause/stop buttons. - Double-clicking Yes on a banner ran its action twice. For the update prompt
this could start two updates and crash the app. - Clearing the token field in Settings didn't actually remove the token. It
came back on the next start. - Editing a tile from the Settings shortcut list could save the changes to a
different tile. - Dragging a wide tile next to another one could drop it on top of a third
tile, which then vanished from the grid. - Lock tiles could unlock when they were asked to lock if the state couldn't
be read. Lock and unlock are now explicit, and the tile's Lock/Unlock
setting is honoured. - The Flat button style showed as Gradient in Settings and was switched to
Gradient on the next save. - Changing climate temperature and then mode or fan speed within half a
second dropped the second change. The same applied to alarm, mower and
vacuum actions. - Changing a tile's type kept settings from the old type. A Light tile turned
into a Scene still sentlight.toggle. - Resizing a duplicated tile resized a different copy.
- Sensor tiles mangled non-numeric states:
12:34showed as12.0:34, and
dates were affected the same way. - Temperatures with two or more decimals lost digits (
20.05showed as
205). - Changes to sensor precision and min/max now apply immediately.
- Recording a per-tile shortcut left the global hotkey dead until Settings
was saved again. - On Wayland, cancelling the shortcut dialog made it pop up again every 30
seconds. - The Linux updater deleted the running AppImage before the new one was
fully copied, so a full disk could leave you with no app. - Button service data no longer gains an
entity_idkey after each click.
Thanks
@HomeRiz for the security report and fixes, the dependency update, the
test suite and the update indicators ยท @niklasthorild for the Nix flake
automation.
Install
| Platform | File |
|---|---|
| Windows | PrismDesktopSetup.exe
|
| Linux | PrismDesktop-x86_64.AppImage
|
| macOS (Apple Silicon) | PrismDesktop-macOS-arm64.dmg
|
| macOS (Intel) | PrismDesktop-macOS-x86_64.dmg
|
Checksums for every file are in SHA256SUMS.