-
Onebox v32.12.0
StableRelease / build-and-release (push) Successful in 29m34sreleased this
2026-09-25 15:04:43 +00:00 | 6 commits to main since this release2026-09-25 - 32.12.0
Features
- Make the SMB storage target password write-only instead of storing and returning it in the clear. The password is no longer part of the target configuration: it is set with the new
setStorageTargetPasswordrequest, stored with Onebox's credential encryption, and every response reports onlypasswordSet.getStorageConfigandupsertStorageTargetreturn no password, the settings dialog no longer pre-fills it, and a configuration that still contains one is refused. Changing an SMB target's server, share or kind removes the stored password. - Give every volume on an NFS or SMB target an explicit
subPathbelow the target's root. The data version moves to0.25.0through the stepstorage-target-credentials, which encrypts stored SMB passwords, rewrites every existing network volume tosubPath: "."(the root it already mounts, so no data moves), and removes credential elements from other stored volume options. A request may name anothersubPath, which must exist on the export; a volume keeps itssubPathacross updates. Restoring a backup from an earlier release drops the mount options it recorded for such a volume. The step is one-way: Onebox releases up to 32.11.0 know data versions only up to0.24.0and refuse a0.25.0ledger by name, so going back to 32.11.0 after the upgrade needs a database copy taken before it; without one, recovery is forward-only.
Fixes
- Stop copying a volume's resolved mount options onto the service record. A volume on an NFS or SMB target is stored as its storage class and
subPath; its mount, with the decrypted password, is composed only when Onebox creates the runtime. Onebox creates such a Docker volume before the runtime and mounts it by name, so container and Swarm service specifications no longer carry the password. Docker's local volume driver keeps it in the volume's options: it mounts with mount(2), and the kernel ignorescredentials=, so there is no credentials file it can read instead. - Refuse storage target values that could add mount options. The server, username, domain, password and every option value of an NFS or SMB target are refused when they contain a comma or a control character, option keys are limited to letters, digits, dots, dashes and underscores, and options may not restate the address, version or identity the target states. Refusals are reported as
storage-target-config-invalidand name the field, never the value. Storage targets now have one typed configuration per kind, and a member the kind does not have is refused. - Backups and database copies from earlier releases contain the SMB password in the clear; change it on the SMB server after upgrading and set the new one on the target.
Downloads
- Make the SMB storage target password write-only instead of storing and returning it in the clear. The password is no longer part of the target configuration: it is set with the new