Skip to content

For IT

Relaix on managed machines: what it does on its own, and the 41 settings you control, through Group Policy and Intune on Windows or a file on Linux.

What it does on its own

  • No telemetry and no online license check. The only connection it makes by itself is the update check, which a policy turns off.
  • Secrets live in Windows Credential Manager (or a password manager, used by reference), never in its files.
  • Its data is in %APPDATA%\Relaix; crash reports stay on the computer and are never sent.
  • Self-contained: no .NET install needed, and nothing is unpacked to a temp folder at start.

Policies

Copy the ADMX and ADML files that come with Relaix into C:\Windows\PolicyDefinitions (or your central store) and the settings appear under Relaix. With Intune, import the ADMX as a custom template, or set the values under HKLM\SOFTWARE\Policies\Relaix (DWORD 1/0 for on and off, strings for text). People see what's set under "Organization policies" in the command palette, and settings you decide are greyed out.

PolicyNot configuredWhat it does
AllowLegacyAlgorithmsOnOff: no host can use legacy algorithms (SHA-1, CBC, ssh-rsa), whatever its own settings say.
RequireFipsAlgorithmsOffOn: SSH uses only FIPS-approved algorithms (AES, SHA-2, NIST curves, RSA). Servers that offer nothing else can't be reached.
StrictHostKeysOffOn: a server whose key isn't already trusted is refused instead of asking the user to trust it.
AllowX11ForwardingOnOff: X11 forwarding is never turned on, whatever the host or folder says.
AllowSshAgentOnOff: "SSH agent" credentials (Windows OpenSSH agent, Pageant) can't sign in.
AllowNonLoopbackForwardsOnOff: local and SOCKS forwards only listen on this computer (127.0.0.1), never on the network.
AllowWebViewsOnOff: web pages (device admin pages) can't be opened in Relaix, directly or through an SSH host.
WebSmartScreenOnOn: Microsoft Defender SmartScreen checks every web page opened (Windows), and users can't turn it off. Off: it never does, so the addresses of internal devices aren't sent to Microsoft. Not set: the user's choice, on unless they turn it off.
AllowVncOnOff: VNC remote desktops can't be opened in Relaix, directly or through an SSH host.
AllowRdpOnOff: RDP (Windows Remote Desktop) connections can't be opened in Relaix, directly or through an SSH host.
AllowCodecDownloadOnOff: Relaix never downloads Cisco's OpenH264 (RDP's H.264 on Linux and macOS), and RDP there works without H.264. On: users may turn the download on in settings (it's off until they do). Windows uses its own decoder either way.
AllowTelnetOnOff: Telnet connections (not encrypted) can't be opened in Relaix, directly or through an SSH host.
AllowFtpOnOff: FTP and FTPS file servers can't be opened in Relaix, directly or through an SSH host.
AllowPlainFtpOnOff: only encrypted FTP (FTPS) opens; plain FTP, which sends passwords and files unencrypted, is refused.
AllowSerialOnOff: serial ports (console cables) can't be opened in Relaix, from the port list or a saved serial host.
AllowRdpClipboardOnOff: the clipboard isn't shared with RDP desktops (nothing copied on either side can be pasted on the other). On: users may turn sharing on in settings (it's off until they do); text and images go both ways, files never.
AllowClipboardFromRemoteOnOff: VNC desktops and programs in terminals (OSC 52) can't put text on this computer's clipboard. On: users may allow it per tab (it's off until they do, and they're asked first). RDP's sharing is AllowRdpClipboard.
AllowNetworkToolsOnOff: Relaix's network tools (ping, traceroute, scanners) can't be used. The subnet calculator still works.
AllowToolServersOnOff: Relaix's servers for network gear (the TFTP server) can't be started.
AllowTerminalFileTransferOnOff: files can't be sent or received inside a terminal (ZMODEM with sz and rz, XMODEM to a device).
ProxyNot setEvery SSH connection goes through this proxy, for example socks5://proxy.corp:1080 or http://proxy.corp:8080.
LicenseKeyNot setThe business license key for everyone on these computers (RLX1.…, from the purchase email). People can't change or remove it.
AllowSavedSecretsOnOff: passwords and key passphrases are asked for each time and never saved (smart cards and agents still work).
AllowCredentialProvidersOnOff: credentials can't take their passwords from password managers (1Password, Bitwarden or Vaultwarden, Azure Key Vault, credential helpers). Connections with such a credential say so: SSH asks for the password instead, the others don't connect.
AllowedCredentialProvidersNot setOnly these password managers can be used, comma-separated: 1password, bitwarden, azure-key-vault, helpers (credential helper programs); none for no password manager at all. The others are hidden and their credentials ask for the password. Not set: all of them (AllowCredentialProviders and AllowCredentialHelpers still apply).
AllowCredentialHelpersOnOff: credential helper programs users add aren't run (1Password, Bitwarden and Azure Key Vault still work unless AllowCredentialProviders is off).
AllowCredentialExportOnOff: credentials can't be exported with their passwords to move them to another computer (Export credentials is turned off). Importing still works.
RequirePairedExportOffOn: an export can only be opened by the computer it's made for (its pairing code), never with a password, so a copied file can't be guessed open.
RequireMasterPasswordOffOn: saved passwords and key passphrases are encrypted with a master password (Argon2id, AES-256-GCM). Until the user sets one, none are saved or used; Relaix asks them to set one at start.
AllowRememberUnlockOnOff: the master password is asked each time Relaix starts, never remembered until the user signs out of Windows.
AllowWindowsHelloOnOff: saved passwords can't be unlocked with Windows Hello; the master password is asked instead. A Windows Hello unlock the user already set up is removed (its key too) when Relaix starts.
LockWithComputerOffOn: saved passwords lock whenever the computer locks or goes to sleep (users can't turn it off).
LockAfterIdleMinutesNot setSaved passwords lock after this many minutes without using Relaix (1 to 1440). Users can't turn it off or make it longer.
AlwaysLogSessionsOffOn: every SSH session is logged to a file (what the terminal shows, never what is typed).
AlwaysRecordSessionsOffOn: every SSH session is recorded (an asciicast .cast file in the log folder: what the terminal shows, timed; never what is typed). Users can't stop it; at the size limit it moves on to a new file.
LogFolderNot setWhere session logs go (a full path; environment variables like %USERPROFILE% are expanded).
AuditToEventLogOnOff: connection events are not written to the Windows Event Log (Applications and Services Logs > Relaix).
AuditToFileOnOff: connection events are not written to the local audit file.
AuditFolderNot setWhere the local audit file goes (a full path; environment variables are expanded).
AllowUpdatesOnOff: Relaix never checks for or installs updates (it makes no connection of its own). Deploy new versions yourselves: Intune, MSIX or the installer.
UpdateChannelNot setWhich updates Relaix installs: stable (releases) or beta (betas too). People can't change it.

Linux (and macOS)

The same settings come from a file instead of the registry: /etc/relaix/policy.json, one JSON object with the policy names above and their values. Put it there with whatever you manage machines with (Ansible, Puppet, Salt); leave it owned by root and not writable by others, so people can't change it. The macOS build, when it ships, reads the same file.

{
  "AllowTelnet": false,
  "AllowPlainFtp": false,
  "RequireMasterPassword": true,
  "LockAfterIdleMinutes": 15,
  "LogFolder": "/var/log/relaix"
}

On and off are true and false, minutes are numbers, and folders and addresses are text. A value that can't be used is shown in a message when Relaix starts, with what applies instead: an on/off one is treated as its safer value. A file that isn't valid JSON locks every on/off policy to its safer value until it's fixed. A few policies only mean something on Windows: AllowWindowsHello and AuditToEventLog (the audit file works everywhere). AllowCodecDownload only matters off Windows, where RDP's H.264 decoder is downloaded.

Audit trail

Connections, failed connections, host keys trusted, refused or changed, file transfers, port forwards, commands run on servers, macros and credential exports each have a fixed Event ID in the Windows Event Log (Applications and Services Logs > Relaix) and a line in a local audit file. Never passwords, keys or what was typed. Forward the Event Log to your SIEM for a record users can't change. Session logs and recordings can be required for every SSH session.

Smart cards

A "Certificate" credential uses the card's certificate (RSA 2048 and up, or ECDSA P-256, P-384, P-521); Windows asks for the PIN when Relaix signs in. Kerberos (GSSAPI) isn't supported yet.

Deploying

A deployment guide comes with the release: the MSIX package for Intune or Add-AppxProvisionedPackage, the policy files, and the Event Log registration. The business license key can be set for everyone with the LicenseKey policy.

For Relaix 0.1 previews. Something wrong or missing here? Tell us