Repository navigation
What's new
- Faster sessions. The session view now uploads only the parts of the picture that changed to the
GPU, not the whole desktop on every update. Dragging a window over a Retina-sized desktop went from
20% to 3% CPU in the view, and a blinking text caret from 30 MB to under 1 KB per update. - VNC Low is 16-bit colour. Low quality asks the server for 16-bit colour on top of strong
compression: a third less data from any server. It matters most for a Mac, whose Screen Sharing has
no Tight or JPEG. Over a 100 Mbit link a Retina Mac went from 5 to 10 updates a second. - No more stale patches in RDP. Dragging a window around fast could leave bits of the old picture
on screen until something redrew them. Two threads wrote to the window at the same time and lines got
lost; that cannot happen any more, and a large burst of changes ends with one full redraw. - Clipboard, Gliff: nothing moves at connect. Each machine keeps its own clipboard until something
is copied during the session, so a clipboard history on either side never picks up what the other
held. A new per-connection switch, Copied passwords, also shares what a password manager copies (off
by default, never synced, not set by groups). - Clipboard, RDP and VNC: when the clipboard here is cleared (a password manager clearing a copied
password, for example), or you copy something else while the session is not focused, the server loses
what it was offered too. Switching Clipboard off mid-session does the same. A copy made on the server
itself stays there. VNC now behaves like Gliff at connect. - Hotkey windows hang from the top edge of the screen, like Omarchy's console, and are in place
before they slide in. - RDP at 125% or 150%: the picture starts on a whole screen pixel, so fonts no longer look
pixelated in a tab of an odd width. - Measuring: VNC and RDP sessions write a
stats:line to their log for each busy second (updates,
data, decoding time), to see where a slow session's time goes.
Security review
The changes since 0.9.16 were reviewed against docs/security-review.md, and the Reviewer reviewed every
commit and ran the omarchy-plugin-security skill on them; nothing open. Checked in particular:
- Copied passwords is this computer's own: it is in
LOCAL_KEYSandGROUP_LOCAL_SETTINGS, so no
sync, import or group file can switch it on, and a connection with it on counts as signing in here, so
a synced change of its address waits for you. - Rectangles from a server or session are clipped to the picture before anything is uploaded; the
view'sview-statsline is checked to be digits before it is logged. - The 16-bit picture buffer is sized from the same checked desktop size as the 32-bit one.
- The clipboard watch (
wl-paste --watch) only reports that the clipboard changed, never reads its
contents into OMARemote, and ends with the window that started it. - The session link is now safe to write from two threads; a write that fails shuts the socket down and
leaves closing it to the main thread.
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.17/omaremote-0.9.17-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.17-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.17/omaremote-0.9.17-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.17-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.