Repository navigation
OMARemote 0.9.15
What's new
A security release. Nothing changes in how OMARemote looks or works.
- connections.json, last-connected.json and session logs are read through
omaremote-session read.
It reads only ordinary files, with size, nesting and count limits, so the window never reads
them whole itself. The bar plugin usesread favourites(plugin 0.4.17). - connections.json holds at most 2000 connections, 200 groups, 200 credential sets and 2000 in the
trash. Sync, import and the window add no more, and say why. - Sync merges in linear time: a round against a full library takes seconds, not minutes. A sync
file holding more than a library would is not read. Only deletions of what this system knows
are kept, and a deletion wins over a stale copy whichever file is read first. - Opening a connection while OMARemote is closed (the bar plugin's click) waits for the library
to load. An unreadable library is retried.
Security review
The Reviewer reviewed this work in four rounds, then ran a second full omarchy-plugin-security
sweep of the whole tree (backend, QML, native code, packaging, CI). Every finding was fixed with a
test: JSON parsing that could escape on deep nesting, a FIFO that could hang the last-connected
stamp or a session record rewrite, FileViews that read whole files on every change, and least
privilege in the release workflow. One hardening item (bounded reads of the theme files) is
deferred.
OMARemote is in early development: it works day to day, but expect rough edges. Please report what you run into: https://github.com/RFdeGroot/OMARemote/issues
Install on Omarchy, on Intel/AMD (x86_64) or Apple Silicon (aarch64); pacman pulls in every dependency:
curl -LO https://github.com/RFdeGroot/OMARemote/releases/download/v0.9.15/omaremote-0.9.15-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.15-1-$(uname -m).pkg.tar.zstThe package is signed with OMARemote's release key; OMARemote's Update button checks that before installing. To check it by hand, with the key from packaging/arch/omaremote-release.gpg in the repository: curl -L -o omaremote.sig https://github.com/RFdeGroot/OMARemote/releases/download/v0.9.15/omaremote-0.9.15-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.15-1-$(uname -m).pkg.tar.zst. Keep the signature under that other name: pacman checks a .sig it finds beside the package against its own keyring, which does not have OMARemote's key, and refuses the install.
Updating from an earlier release works the same way: pacman upgrades in place. Restart OMARemote afterwards.
Or build it from source with the attached PKGBUILD: makepkg -si. See the README for more.