Repository navigation
WebSSH 3.2.0
WebSSH 3.2 can be installed from an Unraid template, keeps its application
code read-only for the service user, and keeps custom-UID recovery volumes
provisioned across container recreation. Route settings gain a direct way to
manage jump hosts.
Highlights
- Unraid template.
unraid/webssh.xmlinstalls the official image with
the homelab settings ofdocker-compose.ymland runs it asnobody:users
without Linux capabilities and without setuid privilege gains. Unraid
creates the appdata folders for that user, so the first start needs no
manual permission step. A test keeps the template's ports, paths and
variables in sync withdocker-compose.yml, and the container checks start
the shipped template. See
Install on Unraid. (#346) - Read-only application code. Code under
/appbelongs to root and is not
writable by the service user; only/app/dataand/app/recoveryare. A
compromised process can no longer change code that later starts or health
checks run. (#346) - Custom-UID recovery volumes. The image ships a placeholder in
/app/recovery, so a recovery volume provisioned for a customuser:keeps
its ownership when the container is recreated before its first start.
(#345) - Clearer start-up errors. A data directory owned by another user stops
the container with the requiredchowncommand. A numeric user without a
writable home gets a private Gunicorn runtime directory instead of a control
socket error. (#346) - Manage jump hosts from route settings. The connection dialog and the host
editor offer a "Manage jump hosts" button next to the SOCKS5 proxy button.
(#343)
Project maintenance
- A weekly job removes untagged image manifests that no tagged image
references, after 90 days; tagged versions are never deleted. (#341) - Commits and pull request text are checked for tool attribution. (#342)
- Releases use lightweight tags on the merged candidate commit, so GitHub shows
them as verified. (#344) - The v3.1.0 delivery evidence is recorded. (#340)
Upgrade and recovery
No data format changes. Existing Compose files, named volumes and bind mounts
keep working; the image still runs as UID/GID 1000. Rolling back to 3.1.0 with
the same volumes works.
Behaviour changes to check before upgrading:
flask --app start:app backup create --confirm-offlinewithout
--destinationno longer writes into/app. It uses the private directory
underBACKUP_TEMP_DIRand prints the archive path; with the supplied
Compose files that is the persistent recovery volume.- A custom write path under
/appwithout its own volume, for example
DATA_DIR=/app/custom, now stops the container at start. Such data was lost
on every image update before. Mount a volume at that path or keep the
defaults. - Derived images that write into
/appat runtime as the service user must
write to a mounted volume instead.
See Upgrading, Rollback, and FAQ.
Verified delivery
- Tag commit:
5c5c8edd53ca547d32add20edef5bc3292b526cf. - 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 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.2.0and:3.2;latestpoints to
the same image. The3.1tag remains on 3.1.0. - Immutable image:
ghcr.io/bifrost0x/webssh@sha256:c2edfb472515a896db38eddf52b44aafbbb5a31530090be41cfefea4ff486f09. - The published image reports version 3.2.0 and starts as UID 1000. Its
compatible, hardened, custom-UID and Unraid template runtime profiles passed
against the published digest.
Before release, every documented installation path ran on the release tree
fresh and as 3.1.0 to 3.2 to 3.1.0 to 3.2 on the same data, including LDAP
with production and the Unraid template. Acceptance on a real Unraid server
and in the Community Apps submission scan is not inferred from this.
Deployment-specific identity-provider and native-device acceptance is not
inferred from automated CI. Follow the upgrade precautions above and validate
your own configuration.