Repository navigation
Quick start
-
Download the binary for your system from Releases and optionally verify it: put
SHA256SUMS.txtandSHA256SUMS.txt.signext to it and runwrm-pro-… -release-verify SHA256SUMS.txt(signature and SHA-256), or compare the SHA-256 yourself.gh attestation verify <file> --repo vedranius/web-browser-RDM-publicshows which workflow and commit built it. -
Run it:
Linux / macOS / FreeBSD / OpenBSD
chmod +x wrm-pro-v14.14.1-linux-amd64 ./wrm-pro-v14.14.1-linux-amd64
On macOS, if Gatekeeper blocks the file:
xattr -d com.apple.quarantine wrm-pro-*-darwin-*.Windows (PowerShell), or just double-click the
.exe:.\wrm-pro-v14.14.1-windows-amd64.exeLinux AppImage (x86_64 / ARM64)
chmod +x wrm-pro-v14.14.1-linux-amd64.AppImage ./wrm-pro-v14.14.1-linux-amd64.AppImage # On ARM64 use wrm-pro-v14.14.1-linux-arm64.AppImage instead.Open http://localhost:8080. The AppImage runs in a terminal and binds to localhost by default; use
PORTorLISTEN_ADDRto change that. Stop it with Ctrl+C. If FUSE is unavailable, run with--appimage-extract-and-run.Data is stored in
${XDG_DATA_HOME:-$HOME/.local/share}/wrm-pro/, or at your explicitDB_PATH. Replace the AppImage to upgrade; the data and encryption key stay in place. For a boot service use the standalone Linux binary with-install-service.Android (Termux)
pkg install wget wget https://github.com/vedranius/web-browser-RDM-public/releases/download/v14.14.1/wrm-pro-v14.14.1-android-arm64 chmod +x wrm-pro-v14.14.1-android-arm64 && ./wrm-pro-v14.14.1-android-arm64Docker
git clone https://github.com/vedranius/web-browser-RDM-public.git && cd web-browser-RDM-public docker compose up -d # https://<host>:8080 (self-signed certificate)
See Docker for details.
-
Open http://localhost:8080 (or
http://<server-ip>:8080). For voice calls from other computers use HTTPS — the quickest way isHTTPS_SELF_SIGNED=1(see Configuration). -
Create the administrator account (the first account). After that, self-registration is closed: the administrator creates accounts in Admin panel → Users (or opens registration in Security policies).
-
Click + Connection, enter host, user and password or key, then double-click the connection to open it.
On the first start WRM creates, next to the database:
| File | What it is |
|---|---|
remote_manager.db |
SQLite database (users, connections, shares, audit log). Mode 0600. |
remote_manager.db.key |
Random 256-bit key that encrypts stored passwords, private keys and 2FA secrets. Mode 0600. Back it up separately — without it stored secrets cannot be decrypted. Or set your own key with ENCRYPTION_KEY / ENCRYPTION_KEY_FILE. |
recordings/ |
Terminal session recordings (YYYY/MM/<id>.cast.gz, mode 0600), created when the first session is recorded. Location: WRM_RECORDINGS_DIR. |
Locked out? ./wrm-pro-… -reset-password admin prints a new temporary password (add -reset-2fa to also turn off two-factor authentication). Depending on the security level it works only while WRM is stopped or needs a confirmation, see Password reset on the server.
WRM writes from one mail account (Admin panel → E-mail), to confirm users' addresses and to send security notices.
| Preset | Server | What it needs |
|---|---|---|
| Gmail |
smtp.gmail.com:587, STARTTLS |
2-Step Verification on the Google account and an app password; the user name and the sender are the Gmail address (or an alias set up in Gmail) |
| Outlook.com |
smtp-mail.outlook.com:587, STARTTLS |
two-step verification on the Microsoft account and an app password |
| Microsoft 365 |
smtp.office365.com:587, STARTTLS |
the tenant must allow authenticated SMTP (SMTP AUTH) for the mailbox; many keep it off, then use the organisation's relay |
| Other SMTP server | as your mail administrator gives it | STARTTLS (587), TLS (465) or none (only a relay on the same machine); without a user name WRM sends without signing in |
- It works the same for WRM on your own computer and on a server, as long as that machine reaches the mail server.
-
WRM's address for links (e.g.
https://wrm.example.com) goes into the links in mail; WRM never takes it from the request. - The password is encrypted at rest and never sent to the browser. Changing the server or the user asks for the password again, a password is sent only over STARTTLS/TLS (or to a relay on the same machine), and the sender name cannot contain line breaks.
- Send a test message sends at once with the saved settings, to your own confirmed address or else to the sender address (never to an address typed in, so the button cannot mail anyone else), and explains a failed Gmail/Microsoft login. Recent messages lists what was sent, is waiting or failed (with the error).
- Mail goes through a queue (
mail_outbox) that the running server delivers with retries (1 min, 5 min, 30 min, 2 h, 6 h; given up after six tries); messages are kept 30 days. -
Users' addresses: Settings → Security → E-mail address sends a link valid for 24 hours that works once; the address is used once it is opened. Changing or removing it needs a fresh password/2FA confirmation, and a confirmed previous address is told about the new one. Administrators set an address in Admin panel → Users → ⋯ → Set e-mail address (also confirmed by the user) and see it in the user list. Policy
user_email_self(on) lets users set their own. -
Security notices (policy
mail_security_notices, on) go to a confirmed address: password changed, reset by an administrator or withwrm -reset-password(sent at once even while WRM is stopped), two-factor authentication turned on or off (also by an administrator), new e-mail address. Each message is in English and Croatian. - Audited:
admin.mail_settings_changed,admin.mail_test,user.email_change_requested,user.email_verified,user.email_removed,admin.user_email_set,admin.user_email_removed.
These use the same mail account and need WRM's address for links in Admin panel → E-mail.
-
Forgot password? on the sign-in page asks for a user name or a confirmed e-mail address and mails a link to
/?reset=…that is valid for one hour and works once. The answer is the same whether or not an account matched, so the form does not reveal accounts. A user gets at most one link every two minutes, and one address may ask five times in 15 minutes.- On the link the user chooses a new password (the password rules apply). An account with two-factor authentication must also enter a code or a recovery code, so a mailbox alone is not enough. Every other sign-in of the account ends, the user then signs in normally (2FA included), and a security notice confirms the change.
- Never offered to: accounts without a confirmed address, disabled accounts, directory (LDAP/AD) and single sign-on accounts, local accounts while local sign-in is limited to break-glass administrators, and anyone but break-glass administrators during a lockdown.
- Policy
password_reset_mail(Admin panel → Policies → E-mail):all(default),users(not administrators, required at the Enterprise level, so taking over an administrator's mailbox is not enough) oroff.
-
Invitations. Admin panel → Users → New user takes an e-mail address. With Send an invitation, WRM mails a link to
/?activate=…valid for three days: the user chooses the password there, and opening it confirms the address. No password is shown to the administrator. Without an invitation, the address is confirmed by the usual link and the password is given as before. -
Self-registration (when registration is open): with mail set up and the policy
registration_verify_emailon (default), the form asks for an e-mail address and the account starts once the link sent to it (valid 24 hours) is opened. Until then signing in says to confirm the address first. Accounts never confirmed are removed after a week; an administrator can also enable one in the user list (marked registered, e-mail not confirmed yet). - Audited:
auth.reset_link_requested,auth.reset_link_refused(with the reason),auth.reset_link_used,admin.user_invited,auth.register(withpending_confirmation),auth.account_activated.
Whoever can run WRM's executable against its database on the server can reset any password, including an administrator's. That cannot be prevented completely (the same person can read the database and its key), so WRM makes it loud and, at stricter levels, slow. The setting cli_password_reset (Admin panel → Policies → Accounts → Password reset on the server) decides:
| Value | Level | What wrm -reset-password USER does |
|---|---|---|
alert (default) |
Home | Resets at once and prints a temporary password the user must change. Every administrator gets a security alert. |
stopped |
Business | As alert, but refused while a WRM server uses the database (it writes a heartbeat every 20 s). Stop the service, run the command, start WRM. A refused attempt is reported too. |
confirm |
Enterprise | Files a request and reports it. The reset takes effect when the command is run again and another administrator approved it in Admin panel → Security (with a fresh password/2FA confirmation; nobody approves a reset of their own account), or at once with the user's own current 2FA or recovery code (-reset-code 123456), or after one hour unless an administrator rejected it. A request without -reset-2fa cannot be used to turn off 2FA. |
- Every reset, refused attempt, request and wrong 2FA code is a
security.alert(rulealert_cli_reset, on by default) with the server's host name: it reaches every administrator's inbox and notification channels, the audit log and the SIEM. The reset itself is audited asadmin.user_password_resetwithcliand the mode; requests and decisions asadmin.cli_reset_requested,admin.cli_reset_approved,admin.cli_reset_rejected. - The command runs in its caller's environment, so
WRM_CLI_PASSWORD_RESETandWRM_ALERT_CLI_RESETset there can only make it stricter than what the server stores, never looser. - An AI or MCP session never runs
wrm -reset-password,-reset-2faor-lockdownon a server (hard blockwrm_recovery, also under full access), and a temporary password in a command's output is masked before an AI sees it.
WRM PRO v14.14.1 · generated from the in-app help on every release · screenshots use invented demo data · Repository · Issues
Quick start · What's new · Comparison