Every served install script (Windows/WinPE PowerShell 5.1, Linux and macOS
bash) now looks at the device before acting: a healthy, current agent
enrolled with this server is left alone (Already Installed), an older one is
upgraded in place with its enrollment kept, a failed one (service missing,
disabled, stopped or crash-looping, watchdog down, binary missing or broken,
Windows Installer registration or cache gone) is restarted through the
agent's own initialize and, if that does not help, reinstalled (MSI repair
REINSTALL=ALL REINSTALLMODE=vamus, cache restored from the kept package,
uninstall+install with ProgramData and the registry key set aside as a last
resort; Linux/macOS move files in one by one and re-register the unit or
daemon). The bootstrap token is used only when there is no usable credential
or the agent points at another server, never printed, and masked out of
failure messages. One setup at a time, leftovers of interrupted runs cleared.
Each run ends with one outcome line and exits 1 on failure.
The agent's status verb now prints a JSON line with version, server URL,
credential state (valid/missing/unreadable/other-device) and whether a
bootstrap token is pending, which the scripts read.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ADMX/ADML "Remote View: show the Being Viewed banner" (RemoteViewBanner,
REG_DWORD, default off); MSI property REMOTEVIEWBANNER.
- Package-Agent publishes ExecuteR-Banner.exe (self-contained single file)
into every Windows zip; the MSI installs it under Program Files when
present (HasBanner). The Windows PE portable install removes it.
- Generate-Icons also renders banner.ico from assets/banner-icon-source.png.
- Console: Remote View page shows "Banner On" when the device will show the
banner.
- README: Being Viewed banner (policy, behaviour, security model), policy
and MSI tables, packaging; third-party notices list Windows Forms.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The default (MSI) script detects Windows PE via the MiniNT key and takes the
portable path there, since Windows Installer does not run in WinPE. The
portable path unzips with System.IO.Compression instead of Expand-Archive,
stops a running agent before replacing its files, and registers and starts
the Windows service through the agent's own `initialize` (SCM APIs), now
failing loudly on a non-zero exit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Four sign-in methods, configured in the database and switched per tab:
Built-In accounts (PBKDF2-SHA512, 12+ characters, forced change, older
hashes rehashed), Local Windows Accounts (LogonUser against this server's
SAM, bound by SID and local group SIDs), LDAP/Active Directory
(System.DirectoryServices.Protocols: LDAPS, StartTLS, Kerberos sign and
seal; user/group filters, nested groups; automatic setup on a
domain-joined server with a breaker) and OIDC (code + PKCE, state/nonce/
verifier in the database, ID token validation, group claims, end session).
- Sessions are database rows behind __Host-session (revocable at once,
idle + absolute expiry) with a session-bound CSRF token; failed sign-ins
back off per account and address; step-up guards switching methods.
- People get access only through groups: role bindings name a built-in
group, a Windows SID, an LDAP DN or an OIDC claim=value and bind it to an
ExecuteR role, so permissions and device scope compose across roles.
- Settings › Authentication endpoints per method with If-Match, test
sign-ins, and the guard that keeps a way in; users, built-in groups and
bindings under /api/admin; the break-glass account (INITIAL_ADMIN_* or a
one-time password in the log) and auth-reset recovery.
- Upgrade: users' roles move onto built-in groups, the old OIDC settings
(database or OIDC_* env) and claim mappings onto documents and bindings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Windows install one-liner self-elevated (IsInRole -> write a temp .ps1 ->
Start-Process -Verb RunAs), which Defender flagged as Win32/ClickFix.SZZ - an
"executes commands / auto-elevates" heuristic. The scripts now run in place:
no UAC relaunch, no temp scriptblock, no self-delete. The operator runs the
command from an elevated PowerShell, and the Add device modal states that
prerequisite on one concise line (Windows only; the unix installers already
use sudo). Backend + zip installers and the elevation test updated to match.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two Windows-specific fixes:
- The served script downloads the agent package with System.Net.WebClient
instead of Invoke-WebRequest — far faster for the tens-of-MB package on
Windows PowerShell 5.1.
- Force TLS 1.2 before any HTTPS fetch. The Win+R Run box launches PS 5.1 with
-NoProfile, which defaults to TLS 1.0/1.1 and fails the handshake to a modern
ACME/nginx edge (works in an already-open shell that negotiated 1.2). The
Add Device / Settings one-liners now prepend
[Net.ServicePointManager]::SecurityProtocol='Tls12', and the served script
sets it (and, for a direct self-signed fetch, the accept-any callback that
WebClient honors in both PS 5.1 and 7).
Also restored the automatic self-signed-direct handling in the Add Device and
Settings commands (server-informed via serverInfo.selfSignedDirect — no
checkbox): the outer fetch accepts the cert / curl uses -k only when this
origin is the self-signed listener reached directly.
Verified: generated scripts use WebClient + Tls12, no Invoke-WebRequest, parse
clean; Backend install-script tests pass (19); svelte-check clean.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Trust model (no operator toggle):
- The Add Device modal and Settings drop the "Trust self-signed" checkbox
and the skipVerify plumbing; the command is a plain one-liner.
- The install endpoint decides trust from the server: it auto-installs the
CA whenever self-signed TLS is on (the /api/enrollment/ca 200-vs-404 is the
signal), and only skips download verification when the request arrived over
the self-signed listener directly. Not pinned; a real edge cert validates
on its own. Where TLS terminates follows the URL. Tests updated.
NATS bind address is adaptable, loopback by default:
- Standalone `setup --nats-bind` (default 127.0.0.1) sets the core/monitor/
websocket listeners; open it when an edge proxy on another host must reach
NATS directly. Docker: app services (backend, webui, NATS WS) publish on
127.0.0.1 by default (BIND_EXTERNAL_ADDRESS); the bundled proxy binds
publicly via its own PROXY_BIND_ADDRESS.
Installer:
- Both MSIs add their install dir to the system PATH (removed on uninstall)
and record InstallDir under HKLM\SOFTWARE\ExecuteR[\Server] so the location
can be found later. Both MSIs build clean and the tables verify.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Windows install scripts self-elevate: the install work sits in an $install
scriptblock; already-admin runs it in place (build pipelines just install),
otherwise it is written to a temp .ps1 and re-launched elevated (UAC) with
-NoExit so the result stays visible. No re-fetch, no -EncodedCommand (which
trips AV/EDR), and #Requires -RunAsAdministrator is dropped so the check can
run. The elevated copy self-deletes via $PSCommandPath.
Self-signed chain (root, intermediate, leaf) now carries a
serverAuth-only EKU — this is not a client-auth PKI.
Standalone layout fixes so nothing scatters to the filesystem root:
- Logs never appeared: LogSettings read LOG_DIRECTORY but ServerCli wrote
LOG_PATH. ServerCli now writes LOG_DIRECTORY, and LOG_PATH is accepted as
an alias so a key mismatch can never silently disable file logging again.
- TLS cert dir derived from the DB directory, so it nested at data/db/tls.
A new DATA_PATH pins the data root; TLS now lands at data/tls.
- NATS resolver dir was the absolute '/data/resolver' (C:\data on Windows).
nats-auth init takes --resolver-dir; standalone passes ../data/resolver
(relative to the sidecar's working dir, verified CWD-relative like
store_dir). Container default stays /data/resolver for the volume mount.
- NATS auth secrets move under data/secrets, with the include path updated.
Logs are named after the running binary: ExecuteR-Server-<date>.log /
ExecuteR-Agent-<date>.log, tracking the executable if renamed.
Add Device modal hint kept clean (no elevation call-out).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Agent trust for self-signed servers no longer pins/forces — pinning
breaks if a reverse proxy with a real cert is added later. Instead the
CA is installed into the OS trust store (ServerCaAutoInstall) so
ordinary system validation trusts a direct/local self-signed server,
and a proxy with a real cert later just validates normally with the
self-signed CA sitting unused. Replaces the pinned TlsTrustMode: agent
config ServerCaAutoInstall, ServerTrust.FetchAndInstallCaAsync
(Windows stores / update-ca-certificates / macOS keychain),
CaRefreshService keeps it current across renewals, configure
--install-server-ca, agent MSI CAINSTALL, ADMX toggle, install scripts.
Server certificate SANs now cover the hostname, hostname.<dns-suffix>
for every adapter suffix plus the global domain, every non-link-local
IP on every adapter, and localhost/loopback (verified live).
Swarm stack switches named volumes to STACK_BINDMOUNTROOT bind mounts
(shared storage across nodes), matching the compose conventions.
Verified: solution builds, Backend 100 / Agent 60 tests, svelte-check
clean, agent MSI builds, self-signed boot emits the broadened SANs.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Agent trust for self-signed servers is now abstracted from operators.
The server exposes its public CA chain at GET /api/enrollment/ca; a new
pinned trust mode (TlsTrustMode=pinned) makes the agent fetch, pin,
install and validate against that CA for both enrollment HTTPS and the
NATS WebSocket, and a background CaRefreshService re-pins it across
renewals so trust never lapses. Install scripts, the agent MSI
(TRUSTMODE property), the ADMX template and the Add Device modal all
drive pinned trust for self-signed servers; skip-verify/insecure
remains an escape hatch.
Backend ingest subscriptions (presence, inventory, agent events, job
output/progress) now use a NATS queue group, so multiple backend
replicas share the load instead of each writing duplicates.
Deployment manifests move to IaC/: compose (moved from root, paths
rebased; deploy.sh and docs updated), swarm (replicated stack: Postgres,
3-node JetStream cluster, API replicas + single scheduler worker, shared
key-ring volume), and k8s (namespace/config, Postgres + NATS
StatefulSets, API Deployment + HPA, single worker, WebUI, ingress).
Wiki gains a Scaling and HA page with an HA topology diagram covering
stateless vs stateful tiers, NATS cluster/supercluster, overlay
(Tailscale/NetBird), shared storage (MicroCeph) and service discovery.
Verified: solution builds, Backend 100 / Agent 60 tests, svelte-check
clean, agent + server MSIs build.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The first-sign-in reset now presents only while the password is
literally the built-in default - a custom install-time password signs
straight in and clears a stale must-change flag. Bootstrap tokens
accept validMinutes 0 for no expiry (pipelines), mirrored by a No
expiry checkbox in the Add Device modal and a Never display in
Settings. Both MSI dialogs lose the literal ampersands (NoPrefix
labels render & as-is), get much shorter texts with real line
spacing, and the network page relayouts with room to breathe.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The install endpoint takes skipVerify=1 instead of auto-detecting: a
self-signed server that later gains a proxy with a real certificate
must not leave agents skipping validation needlessly. The Add Device
modal and the Settings token panel gain a checkbox, pre-selected only
while the server serves its self-signed chain directly. The PowerShell
skip snippet now covers both generations: wildcard
-SkipCertificateCheck defaults on 7+, the ServicePointManager callback
on 5.1 (verified live in both shells).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New TlsSkipVerify agent setting (DWORD, GPO policy key beats local
registry, ADMX template included) accepts the server certificate
without validation on both the enrollment HTTP call and the NATS
websocket — for servers on the managed self-signed chain with no proxy
in front; the connection stays fully TLS-encrypted. Set it via
configure --skip-tls-verify, the agent MSI SKIPTLSVERIFY=1 property
(remember-pattern like the rest), GPO, or the registry directly.
The server detects direct self-signed serving (HTTPS + no forwarded
headers) and the UI one-liners plus all generated install scripts pick
the correct scheme and add the skip-verify bits automatically —
PS5-safe callback on Windows, curl -k on unix — and configure the
agent to match. Proxied deployments are untouched: agents validate the
edge certificate normally.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Add device modal keeps the single/multi flow: multi now takes a
use count (default 1, up to 9999) or an Unlimited checkbox instead of
the hardcoded 100. MaxUses 0 is the unlimited sentinel — enrollment
only counts uses against a positive limit, expiry and revocation still
gate the token, and creation validates the 0-9999 range. The Settings
token form and list follow (0 = unlimited input hint, infinity in the
uses column, Consumed/Revoke logic aware of unlimited).
Changing the count or unlimited flag after generating invalidates the
shown command — limits are properties of the token, so a new one is
issued on the next confirm. Five new endpoint tests cover the sentinel
round-trip, the bounds and the rejections (the test client now sends
the double-submit CSRF header for cookie-authenticated POSTs).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Devices gains an Add device modal (visible with settings.manage): a
horizontal Windows / Linux / macOS selector, a single-use or multi-use
token choice (24-hour expiry), and Generate command — nothing is
created until confirmed; Esc, click-outside or Cancel dismiss without
side effects, and each open starts fresh. The generated one-liner is
copy-ready per platform.
The install endpoint grew unix variants: ?type=linux|osx returns a bash
script that detects the architecture, downloads the matching agent zip
from the same origin, unpacks to /opt/executer/agent, configures
enrollment through the agent''s new cross-platform `configure --url
--token` verb (registry on Windows, agent.json elsewhere) and registers
the systemd unit / launchd daemon. The agent package service serves the
four unix zips alongside Agent.msi/Agent.zip, and both the CI image
bake and the standalone server bundles stage them.
Covered by seven endpoint tests (PowerShell variants, bash variants
with arch detection, token refusal); modal verified live — it issued a
real token and built the Linux one-liner in the shot.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>