Skip to content

OMARemote 0.9.10

Choose a tag to compare

@github-actions github-actions released this 20 Oct 08:32
· 31 commits to main since this release
Immutable release. Only release title and notes can be modified.

What's new in 0.9.10

  • Updates download within limits. The Update button downloads the new package and its signature first, then checks the signature. Until now, those downloads had no size or time limit: a server pretending to be GitHub could keep sending data until your disk was full, before the check ever ran. Each download now has a size cap (64 MiB for the package, which is about 0.5 MB today, and 64 KiB for the signature) and a time limit, and it only goes over HTTPS, redirects included. The same goes for the releases list that OMARemote reads to see whether there is an update for itself or for the bar plugin (4 MiB, one minute).

Thanks

The marketplace reviewer (HANCORE-linux) found this in the bar plugin's install button, in #12133. OMARemote's own updater had the same gap.

Security review

Reviewed everything since 0.9.9 against docs/security-review.md. The only change is this fix.

  • Downloaded before it is checked, now bounded. omaremote-update: curl --max-filesize (which also stops a stream that announces no length, at the cap), --max-time, --connect-timeout, --proto and --proto-redir '=https' on the package and the signature. omaremote-session: the update check and the plugin check read the releases list through one function that reads at most 4 MiB within 60 s in all (a socket timeout alone counts per read, so a slow trickle never tripped it) and refuses a redirect away from HTTPS.
  • The whole class checked. Every other place that reads data from outside already had a byte cap and a deadline: sync and import files, the clipboard, session messages, Gliff. The release workflow's Arch Linux ARM image, also downloaded before its signature is checked, now has a cap and a deadline too.
  • New tests: every download carries its cap and deadline, a failed download installs nothing, and a list past the cap, a trickle past the deadline and a redirect to plain HTTP are all refused. They fail without the fix.
  • The plugin uses the same limits; they are now part of docs/plugin-interface.md.

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.10/omaremote-0.9.10-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.10-1-$(uname -m).pkg.tar.zst

The 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.10/omaremote-0.9.10-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.10-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.