Repository navigation
OMARemote 0.9.14
What's new in 0.9.14
A security release. Nothing changes in how OMARemote looks or works, unless a file it reads is far larger or stranger than any real one.
- Sync and import tell you what they skipped. When the sync folder or an import holds more than OMARemote takes in, the report says so in one line ("3 files skipped: …") and everything else still comes through.
- If this system's own sync file grows past 4 MiB, the sync report says so: other systems no longer read a file that large.
Security review
Reviewed everything since 0.9.13 against docs/security-review.md. The Reviewer session reviewed every change, ran the omarchy-plugin-security skill over it, and then swept the whole code (not only the changes) for the same classes, so they all ship in this one release.
- Marketplace finding #12587 (HANCORE-linux): sync had no limit on what it read in total. Each file in the sync folder was capped at 16 MiB, but a round read any number of them and kept them all, so whoever can write the sync folder could fill the memory of OMARemote's backend, and the window read the answer whole. A round now takes in at most 4 MiB per system, 16 MiB in all and 64 files (newest first). It reads nothing from a folder holding more than 1024 OMARemote files. The answer to the window is refused above 16 MiB, and the sync command runs with a 1 GiB memory ceiling.
- Found on the way, fixed:
- A file nested very deeply stopped sync for good.
[[[[…crashed the backend's JSON reader with an error nothing caught. Caught, a value 2000 levels deep inside a connection was still merged, and the window's own JSON reader (at most 1024 levels) then refused every round. Every JSON file OMARemote reads is now refused deeper than 64 levels (a real one is about 5). - Import from other clients. A connection the import cannot take (a 400 KB user name, say) still carried its fields to the window: 3 such
.rdpfiles made a 2.3 MB answer. It now shows only a short name. An import reads at most 64 MiB, 500 files and 2000 connections, names at most 100 problems, and its answer is capped like sync's. - Importing an OMARemote export file is held to the same limits as sync.
- The session list.
omaremote-session list(read whole by the window and the bar plugin) read every record in the sessions folder. It now shows the newest 256, each at most 16 KiB. A record could also name its own id:../victimmade the clean-up of old sessions delete a file outside the folder, and a number as id crashed the list. A record now counts only under its own file name, and an id is never a path. - The log view opens only the session's own log, and only when it is an ordinary file.
- Your own configs.
hyprland.lua,~/.ssh/configand OMARemote's managed files are read with a size limit, never through a FIFO (which hung the command), and text that is not UTF-8 is left alone rather than written back changed. A rewritten config gets its permissions on the open file itself. - connections.json. A new one is made readable only by you (0600); the
.brokencopy of a file that does not read is never written through a link. It is still written in place: an atomic write in Quickshell 0.3.2 makes the window reload the old text right after saving the new. - Hyprland's answers (window and monitor lists) are read up to 8 MiB with a deadline; the folders walked for window rules and SSH keys have a file limit.
- The release build's container is pinned by digest, as its actions already were by commit.
- A file nested very deeply stopped sync for good.
- Tests that fail without each fix: the sync limits (count, size, total, nesting, the answer, the memory ceiling), the import limits and refused entries, the session ids and log paths, configs that are a FIFO or not UTF-8, and connections.json's mode and
.brokencopy against the real Store in Quickshell.
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.14/omaremote-0.9.14-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.14-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.14/omaremote-0.9.14-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.14-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.