Repository navigation
WebSSH v2.7.0
·
33 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
WebSSH 2.7.0
WebSSH 2.7 improves SSH authentication, persistent-session navigation, and
reviewable file operations, and includes security and dependency updates.
Changes since 2.6.0
- Answer ordinary SSH server
keyboard-interactivechallenges, including PAM
MFA after password or key authentication. Jump-host prompts identify the hop.
This is separate from MFA for the WebSSH account. Quick SFTP retains its
password/key authentication path. (#304) - Follow folders in persistent tmux sessions with the existing synchronization
toggle and explicit Bash prompt setup. The helper is activated manually in
the intended shell, preserves prompt configuration, and does not edit shell
startup files. Synchronization waits when the prompt is uncertain. (#300, #302) - Use session-local tmux mouse scrolling and choose persistent sessions
explicitly instead of having tmux preselected. (#293) - Manage reusable commands more easily and preview bounded recursive SFTP
permission changes before applying them. File and folder modes remain separate;
SFTP chmod is still disabled by default. (#291) - Keep existing command encodings compatible and validate profile startup modes.
(#299) - Match login and workspace branding to the selected theme, with responsive
background scenes and updated product screenshots. (#292, #294) - Harden remote protocol bounds, account storage access, backup coordination,
and restore/maintenance fences. (#295, #296) - Refresh Python, browser, container and CI dependencies, including pyasn1 and
the development-only minimatch security fix; repair the disposable LDAP lab.
(#295, #297, #307, #308) - Distribute WebSSH under Apache License 2.0 with retained attribution and
third-party notices. Bundled components keep their own licenses. (#298, #299) - Refine README content while retaining its centered header, product tour and
screenshot gallery; keep detailed setup and operational guidance in the Wiki.
Upgrade notes
- Back up the complete data volume, matching application secret, external
authentication secrets and deployment configuration. Keep the previous
immutable image digest for rollback. - Use Compose files from the same published release. Pin the image to
ghcr.io/bifrost0x/webssh:2.7.0, or use its verified digest below.
The default Compose file followslatest. - Recreate the service with your existing overlay list and persistent volumes.
Reload already-open browser tabs to load the matching SSH authentication UI. - Check
/health,/ready, local and configured external sign-in, stored keys,
host-key trust, direct SSH, and a small SFTP transfer. Test PAM MFA against
your server's actual authentication policy. - If using tmux folder synchronization, follow the explicit Bash activation
instructions and confirm readiness at an empty prompt. It is opt-in and is
not installed persistently on the remote host.
Exactly one Gunicorn gthread worker remains required. SMB, Tailscale SSH,
SFTP chmod and server mutations retain their explicit activation requirements.
Standalone SFTP does not gain interactive MFA. The 2.6 parameterized argv
command-set downgrade boundary still applies; changing the image alone does not
reverse stored formats. See upgrade and rollback,
SSH authentication,
tmux setup, and
licensing.
Verified delivery
- Tag commit:
271c5fca33f74ba3ea108ae44549c910f6de7bbb. - Tag CI and native image publication passed. A browser persistence test initially timed out; the failed gate passed on a targeted rerun of the same commit, and five additional local repetitions passed.
- Native Linux AMD64 and ARM64 images passed fixable High/Critical vulnerability and runtime gates. Both retain SPDX SBOM and SLSA provenance, checked directly in GHCR.
- Version tags:
ghcr.io/bifrost0x/webssh:2.7.0and:2.7. - Immutable image:
ghcr.io/bifrost0x/webssh@sha256:1a9ac06d0aca3e88bb8f48d0395b8f87e39d33cb2f19be437cca2b8e193aa5d2.
Deployment-specific identity-provider, native-device, upgrade and recovery acceptance is not inferred from automated CI. Follow the upgrade precautions above and validate your own configuration.