Repository navigation
OMARemote 0.9.11
What's new in 0.9.11
- The update check gives up on time, whatever the server does. 0.9.10 gave the releases list (which OMARemote reads to see whether there is an update for itself or the bar plugin) a one-minute limit, but that limit only started once the server had sent its headers. A server sending those headers very slowly could keep the check waiting far longer. The minute now covers the whole request, headers and redirects included.
- A garbled answer no longer breaks the check. If the server's answer was not valid HTTP, the update and plugin checks stopped with an error instead of reporting "no update found". They now treat it like any other failed download.
Thanks
The Reviewer session found both while reviewing 0.9.10's download limits.
Security review
Reviewed everything since 0.9.10 against docs/security-review.md. The only change is this fix.
- The deadline covers the whole transfer.
fetch_jsoninomaremote-sessionnow runs the request (connecting, status line, headers, every redirect and the body) in a background thread and gives up when the deadline passes. The byte cap and the deadline still hold inside that thread, so a body that keeps coming stops there too. A thread stuck in the headers is left behind; that is safe because the update and plugin checks are short command-line runs that exit right after. - Errors stay errors.
http.client.HTTPException(a bad status line, a header line that is too long) becomes anOSError, which both checks already handle. - New tests use a real local server: one that sends its headers a byte at a time (11 s past a 0.5 s deadline before the fix) and one that sends a garbled status line (a traceback before). Both fail without the fix.
- The lesson in
docs/security-review.mdnow says that a deadline covers headers and redirects, not only the body.
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.11/omaremote-0.9.11-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.11-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.11/omaremote-0.9.11-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.11-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.