Skip to content

OMARemote 0.9.9

Choose a tag to compare

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

What's new in 0.9.9

  • VNC desktops are solid again. Some VNC servers, macOS Screen Sharing among them, showed up see-through: your own wallpaper shone through the remote windows. A VNC pixel has four bytes, and the fourth is padding that a server may fill with anything. OMARemote showed the picture as if that byte were its opacity. It now sets that byte to fully opaque in every part of the screen the server updates, and the colours stay exactly as sent.

Thanks

This fix is the work of xiemin (@peterxiemin), in #3. They found the cause on a 5120x2880 macOS session and wrote a test with a mock VNC server that checks every byte of the shared framebuffer. Thank you, xiemin!

Security review

Reviewed everything since 0.9.8 against docs/security-review.md. The only change is the VNC fix: the server's pixels are written into OMARemote's own framebuffer, only inside the rectangle the server just updated.

  • No write outside the framebuffer. libvncclient refuses a rectangle that does not fit the desktop and ends the session ("Rect too large") before it reaches OMARemote. The desktop itself is at most 8192 pixels a side (since 0.9.7).
  • No new cost a server could not already cause. The pass over the rectangle is cheaper than decoding it: about 6 ms for a whole 5K screen.
  • The new test talks to a mock server on 127.0.0.1 only.

Nothing found.


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.9/omaremote-0.9.9-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.9-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.9/omaremote-0.9.9-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.9-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.