Skip to content

WebSSH v3.1.0

Choose a tag to compare

@bifrost0x bifrost0x released this 14 Nov 16:36
· 10 commits to main since this release
Immutable release. Only release title and notes can be modified.
4eac73c

WebSSH 3.1.0

WebSSH 3.1 adds per-host SOCKS5 proxy routes, automation through saved jump
hosts and browser login management, and makes everyday connection, command
and recovery work easier to reach. It also tightens the page script policy and
restore handling and updates dependencies.

Highlights

  • SOCKS5 proxy routes. Saved hosts can select a reusable, user-owned SOCKS5
    proxy for the terminal and its session SFTP channel, including proxy password
    authentication, reconnects and persistent sessions. Proxy endpoints pass the
    SSH network policy; a missing, changed or failed proxy never falls back to a
    direct connection. Proxy passwords use the encrypted credential store. SOCKS
    username/password authentication itself is unencrypted between WebSSH and
    the proxy. (#334, #336, #337)
  • Automation through saved jump hosts. Hosts behind one saved jump host are
    valid automation targets, with the network policy, verified host keys and
    separate credentials on both hops. Changing the jump host invalidates pending
    runs and schedules. Finished runs can be deleted, and runs on several hosts
    can be compared per step. Terminal tabs can be named. (#319, #320)
  • Updates and restart status. A new read-only workflow template reports the
    restart marker and, on Debian/Ubuntu, pending updates without sudo or writes.
    It runs only when a user starts or schedules it; while a restart hint is shown,
    each login rereads only the restart marker. (#320, #321)
  • Browser logins and access transparency. Users list their active browser
    logins and revoke selected or all other logins. Disabling an authentication
    feature previews affected accounts and MFA loss first; deleting a personal
    host-key entry shows the trust that remains. Multiline and control-character
    input to several sessions requires a session-bound preview. (#333)
  • Task-first overview and workspace presets. Session, favorite and
    recent-host shortcuts, a first-connection checklist, clearer command details
    and account-owned workspace presets, listed directly in the Layout menu.
    Presets store host references and pane choices, never credentials or
    commands. After a portable restore, a recovery checklist guides
    re-provisioning. (#332, #333, #335)
  • Support reports with an exact preview, generated locally only on request.
    (#333)
  • Version display. Signed-in users see the running version and source
    commit in the account menu and Settings; sign-in pages do not show it. (#327,
    #328)
  • Project support links in Settings and the account menu. Administrators
    can hide them under Administration → Integrations. (#331)
  • Interface languages. Remaining English labels in the workspace, file
    manager and quick connect are translated. (#331)

Security and maintenance

  • The page script policy is script-src 'self'; inline scripts and handlers
    moved to static files. (#320)
  • Restore ignores logs/ and tmp/ in archives, so an edited backup cannot
    replace the audit log. (#320)
  • Authlib 1.9.5 (includes the 1.9.3 security fix), python-socketio 5.18.1,
    Flask-SocketIO 5.7.2 and the Python 3.14.10 base image. Dependabot Python
    locks are regenerated with the repository lock script. (#324, #325, #326, #328)
  • Architecture diagrams, README entry point and the product-site tour are
    updated for version 3. (#318, #329, #330)

Configuration

New optional settings; existing Compose files keep working unchanged:

  • SOCKS_REMOTE_DNS_ALLOWLIST: exact names a SOCKS5 proxy may resolve while
    internal targets are blocked. Other names are resolved locally and sent as
    validated addresses. It is separate from PROXY_JUMP_REMOTE_DNS_ALLOWLIST.
  • SOCKS_PROXY_MAX_RECORDS (default 100): SOCKS5 proxies per user.

See the Configuration reference and
SOCKS5 proxies.

Upgrade and recovery

Preserve the complete persistent data and recovery volumes before upgrading
and keep the 3.0.0 image pinned by version or digest. The upgrade adds
database columns and a per-user socks_proxies.json store; existing data is
retained.

Roll back only by restoring the matching pre-upgrade volumes with the 3.0.0
image. Do not start 3.0.0 on data already used by 3.1: it does not know SOCKS5
routes and would connect routed hosts directly.

Portable backups include SOCKS5 proxy metadata and exclude proxy passwords,
like other saved remote passwords. Reload open browser tabs after upgrading.

Changes from 3.0.0

Verified delivery

  • Tag commit: 4eac73cbc319206bce7887e8dba0643a8b0c7ad5.
  • Tag CI and native image publication passed: the full test suite,
    browser end-to-end, SSH and SMB integration, container upgrade, threading
    and Redis rate-limiter tests.
  • Native Linux AMD64 and ARM64 images passed the fixable High/Critical
    vulnerability and hardened runtime gates. Both carry SPDX SBOM and SLSA
    provenance and the tag revision label, checked directly in GHCR.
  • Version tags: ghcr.io/bifrost0x/webssh:3.1.0 and :3.1; latest points to
    the same image. The 3.0 tag remains on 3.0.0.
  • Immutable image: ghcr.io/bifrost0x/webssh@sha256:8714d603a359b7fb9dd210cddf1d8afaaef1b405b4ddfbfc7f3a275bddc13a9f.
  • The published image starts healthy as a non-root user.

Upgrade from an existing 3.0.0 data volume and rollback were not exercised
manually beyond the automated container upgrade test. Deployment-specific
identity-provider, native-device and SOCKS5 proxy acceptance is not inferred
from automated CI. Follow the upgrade precautions above and validate your own
configuration.