Repository navigation
OMARemote 0.9.8
What's new in 0.9.8
A Windows desktop that locked itself comes back signed in. Windows locks a session after a while without input. Then you had to type your password inside the session again, which is especially clumsy in a hotkey window meant for quick access. A reconnect with your saved credentials brings you back into the same session past the lock screen, with your programs and work as they were. OMARemote now does that for you:
ctrl+alt+rreconnects an RDP session in place, in a tab, an own window or a hotkey window. The old session stays on screen until the new one is up, then the new one takes its place. One that takes longer than 5 seconds is shown anyway, in case it is asking for a password, with the old one running behind it until it connects. A reconnect that fails goes back to the old session.- Unlock on return (connection or group editor, RDP, off by default): when you come back to a session after 5, 10, 15, 30 or 60 minutes away (another tab, another window, a hidden hotkey window), it reconnects. RDP does not tell whether Windows locked, so pick the remote's own lock time or a bit more. A reconnect that was not needed costs a few seconds.
- The password is never typed into the session. A reconnect is a new sign-in, where FreeRDP hands it to Windows over NLA, exactly as when you first connect. Without a saved password you are asked as usual. The remote's own lock stays: while you are away it locks as its owner wants.
Security review
Reviewed against docs/security-review.md, and by the Reviewer session in three rounds (all findings fixed before this release: closing a tab or moving it to a window during a reconnect could leave a session running unseen; a replaced session's end was reported as a failure).
- Unlock on return is this system's own. It signs in by itself, so it never syncs or exports, on connections and groups, and a sync or import file can neither set nor clear it (tested). A value other than a whole number from 1 to 1440 counts as off.
- No new credential path. A reconnect is an ordinary launch of the connection as saved here: a synced address change still waits for your confirmation, and the password goes only to FreeRDP's stdin and Windows' sign-in.
- It only reconnects when you are back (the session's tab or window has the focus again), never while you are away.
- A "keep the remote awake" option was considered and dropped: it would defeat the remote's own lock policy.
- Left as is: a reconnect started in an own window that is closed before the new session shows up leaves that session running in the background. The manager adopts it into a tab when it starts and stops it when it closes, and the bar lists it.
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.8/omaremote-0.9.8-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.8-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.8/omaremote-0.9.8-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.8-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.