This release lets you play and delete each terminal of a multi-terminal session, makes replacing an offline device on accept visible and permissioned, and closes a round of security gaps found in the November audit. Three changes need attention before you upgrade: agents refuse a plain http:// server address, a reverse proxy must append the client to X-Forwarded-For, and the default SHELLHUB_BIND_ADDRESS is now empty.
Agents refuse a plain http:// server address
Upgrading? An agent pointed at
http://on anything other than loopback no longer connects. Move the server to HTTPS, or setSHELLHUB_ALLOW_INSECURE_SERVER=truein the agent's environment to keep the old behavior with a warning.install.shforwards the opt-in for Docker, Podman, standalone and WSL; the snap refuses it.
The agent trusts the server for public-key logins. Over clear text, anyone on the network path could pose as the server, get a root shell on the device and read its device token (#8014).
Reverse proxies and published ports
Upgrading? A reverse proxy in front of ShellHub must be listed in
SHELLHUB_PROXY_TRUSTED_IPSand append the client toX-Forwarded-For.X-Real-IPis no longer read, so a proxy that sets only that header makes every client appear at the proxy's address.
The server now resolves the client the same way with or without the bundled gateway: it walks X-Forwarded-For right to left and takes the first hop outside the trusted list. Before, behind an HTTP proxy every client showed up at the proxy's address, and with the gateway off a trusted peer's X-Real-IP was taken as is (#8020).
Upgrading?
SHELLHUB_BIND_ADDRESSnow defaults to empty, so ports 80, 443 and SSH are published on every address, IPv6 included. Set0.0.0.0for IPv4 only. Docker Compose 2.18 or later is required.
Only port 80 honored SHELLHUB_BIND_ADDRESS; HTTPS and SSH listened on every interface whatever you set. All three ports now take the address (#8024).
Every terminal of a session can be played and deleted
The console only reached the first terminal of a session. When a session opens two or more, the session page now shows a tab per terminal, and each recording plays, downloads and deletes on its own. Deleting from the session list removes every terminal's recording. A session stays recorded until its last terminal is deleted (#8050).
Replacing an offline device on accept
Accepting a pending device with the same MAC as an offline accepted device replaces it: the new device takes the old one's name and sessions. Nothing recorded this before, and any operator could do it. Now:
- A manual or pairing accept replaces only when the caller may remove devices and sends
replace: true. Without the permission it answers 403; withoutreplaceit answers 409 naming the device. The console asks before replacing (#8039) - A provisioning key replaces when its
replace_offline_devicessetting is on, the default. The webhook callback follows the key - Each replacement is written to the key's history, and the device shows the latest one
Session timelines no longer keep secrets
The SSH server stored the raw body of every request it did not decode, so ssh -o SetEnv=TOKEN=... left the secret in the session's events, even with recording off. env requests are no longer stored, and unknown request types keep only their name (#8027). A migration deletes the env events and payloads already stored. On a large session_events table it scans the table once while the server starts (#8028, #8035).
The timeline also holds the command of each exec, so GET /sessions/{uid} now returns it only to administrators and owners, who can replay recordings (#8029).
Account and approval hardening
- Changing your email requires your password, and on Cloud the new address must be confirmed from a mailed link. A new recovery email is held until confirmed on Cloud, and MFA accounts are asked for a code (#7972, #8017)
- Wrong passwords during web terminal re-authentication and
PATCH /api/usersnow count toward the lockout, like sign-in (#8040) - The console can no longer be framed, and HTTPS responses carry
Strict-Transport-Security. An SSH key approval writes the key only once the code typed in the terminal matches, so a page that tricks you into clicking "Add key" gets nothing (#7965) - SFTP refuses accounts whose login shell confines them (
nologin,false,git-shell, restricted shells). SetSHELLHUB_SFTP_ALLOW_RESTRICTED_SHELLS=trueon the agent to allow them. In connector mode, exec runs the command through the login shell (#7964) - Concurrent device accepts stay within the namespace and license device limits (#7968)
Licenses can name their domains (Enterprise)
A license can list the hostnames the instance runs under. When it does, devices authenticate only when they reach the server under one of those names, and get a 402 otherwise; agents keep retrying and recover once the license matches. Sign-in, the console and the admin area are unaffected, so an admin can always replace the license. The license banner and the admin license page warn when the browser's hostname is not licensed (#8059).
Also in this release
API changes
PATCH /api/users/{id}/passwordis removed. Change your password withPATCH /api/users, sendingpasswordandcurrent_password(#7997)- SSH identity
expires_inis capped at 365 days (#7961) - SAML sign-ins hand the session to the console through a one-time code (#7980, #8013)
Fixes
- A connection that runs many commands, such as Ansible or OpenSSH
ControlMaster, no longer keeps every ended channel in memory (#7959) - The server closes a device tunnel that opens streams toward it instead of letting them pile up (#8060)
- The connector keeps running when a container disappears (#8034)
- A tag rename that only changes letter case is applied (#7990)
- Changing an access policy records the API key that did it (#7993)
- Updating a user writes only the columns that changed (#8000)
- The agent image ships an apk database, so image scanners see its OS packages (#7998)
- Firewall rule and public key patterns are checked in the console as Go regular expressions, matching the server (#8054)
- Console: the disable-MFA dialog can go back to the authenticator code, MFA dialogs reset on open, sign-in methods refresh after a settings change, username inputs stop auto-capitalizing, a cleared email is handled in the profile modal, unticking a user's namespace limit removes it, queries refused with a client error are not retried, list errors show on access policies and SSH identities, and the command palette lists the sidebar's pages (#7984, #7986, #7987, #7994, #7995, #8026, #8030, #8033, #8037, #8038, #8053)
Cloud
- Each terminal of a multi-terminal session can be deleted on its own, and the recording archiver re-checks under the session lock before cleaning up
- Deleting an account asks for the password or MFA code
- A new email is confirmed by a mailed link, and the old address is told
- MFA reset: a pending code pair is sent again instead of replaced, three wrong pairs cancel the reset, misses are counted atomically, requests are throttled and answered alike, recovery codes work during the lockout, and TOTP guesses outside sign-in count toward it
- SAML: a response is accepted once and only for a request the server sent, the sign-in completes only in the browser that started it, and a SAML identity links to an existing account only after the account confirms it
- An admin email change is checked and both addresses are told; a taken namespace name is reported as duplicated
- Billing: cards are listed when the customer has no default, and the portal answers 400 for a namespace without a customer
Under the hood
- The server's layers and the edition seam are untangled: enterprise features attach through one extension point, error codes map to HTTP statuses in one table, and the namespace device counters are kept by a database trigger (#8044)
- The console's permission table is generated from the Go authorizer, and edition rules live in one table (#8045, #8048)
- Release images are signed by digest and rebuilt on every tag; CI tokens are scoped down and fork PRs run without write access (#7978, #7979, #7999, #8001)
- Go 1.26.11 (#8062) and dependency updates via Dependabot and Renovate
Full Changelog: v0.30.4...v0.31.0