Files
napalm-openmediavault/CHANGELOG.md
T
Christian Manivong d477fb1a76
driver / standard (pull_request) Failing after 14s
driver / lint (pull_request) Successful in 14s
driver / types (pull_request) Failing after 1m13s
driver / test (3.13) (pull_request) Failing after 1m6s
driver / test (3.12) (pull_request) Failing after 1m17s
driver / lowest (pull_request) Failing after 29s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Failing after 2m25s
driver / publish (pull_request) Skipped
feat: personal accounts the way OMV's web UI makes them (NetOrk/netork#1793)
napalm-linux adds and locks accounts with shadow-utils and keys in ~/.ssh.
OMV's sshd lets in only root and _ssh, and OMV keeps a user's keys in its
own database, deploying them to /var/lib/openmediavault/ssh/authorized_keys.
So a new account is made by UserMgmt.setUser in _ssh, one made outside OMV
joins _ssh when it is opened, and keys go through setUser. Each call applies
the modules it made dirty (postfix, ssh) and leaves what was pending in the
web UI pending. setUser takes a plain password, netOrk only the hash, so the
hash is set with usermod -p. The lock stays napalm-linux's expiry.

Checked on a fresh OMV 8 (Debian 13) with the real driver over SSH and
sudo -S: a new account logs in with its key and uses sudo, is refused
after locking with OMV's keys emptied, logs in again after reopening; an
account made outside OMV is let in once it joined _ssh; a module left
dirty before stays dirty.
2026-10-31 23:43:43 +01:00

48 lines
2.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Changelog
All notable changes to this driver. The format follows
[Keep a Changelog](https://keepachangelog.com/), versions follow
[Semantic Versioning](https://semver.org/).
## [Unreleased]
### Added
- Personal accounts the way OMV's web UI makes them (NetOrk/netork#1793), on top of
napalm-linux's `get_local_accounts()`, `add_local_account()` and `lock_local_account()`.
OMV's sshd lets in only `root` and `_ssh`, and OMV keeps a user's keys in its own
database, deploying them to `/var/lib/openmediavault/ssh/authorized_keys/<user>`. So a
new account is made by `UserMgmt.setUser` in `_ssh`, an account made outside OMV joins
`_ssh` when it is opened, and keys are added and removed through `setUser`. Each call
applies the modules it made dirty (`postfix`, `ssh`) and nothing else: changes left
pending in the web UI stay pending. `setUser` takes a plain password, which netOrk does
not have, so the hash is set with `usermod -p`. Like the web UI, `setUser` gives the
account OMV's primary group `users`. Checked on a fresh OMV 8 (Debian 13) with the real
driver over SSH. Requires the napalm-device-types and napalm-linux releases with
personal accounts.
- `set_hostname()` the way OMV's web UI renames the NAS: `Network.setGeneralSettings`
(an FQDN sets the domain too, a bare name keeps it), then `Config.applyChanges` for the
modules the rename made dirty plus the hostname modules already dirty. Changes left
pending in the web UI are not deployed with it. Replaces the inherited napalm-linux
rename (NAPALM/napalm-linux#45), whose `/etc/hostname` and `/etc/hosts` OMV would
regenerate on its next apply.
### Changed
- Python 3.12 is the floor (`requires-python = ">=3.12"`): netOrk runs every driver
on 3.12, so 3.10 and 3.11 are no longer tested (NAPALM/driver-standard#6).
## [0.3.0] - 2026-10-23
The first release on PyPI.
### Changed
- The driver follows the NAPALM driver standard
(https://git.netork.io/NAPALM/driver-standard): CI on Gitea runs ruff, mypy, the
tests on Python 3.10–3.13 and at the lowest declared versions, bandit, pip-audit and
a build check, and a release tag publishes to PyPI. The package now ships `py.typed`,
a README and a LICENSE file. It needs napalm-device-types 4.22.0 and napalm-linux
0.15.0. **Python 3.9 is no longer supported**; napalm-device-types never ran on it.
- Failures the driver deliberately ignores (the OpenMediaVault version, `smartctl` for one
disk, `/proc/mdstat`, `mdadm --detail`, a shared folder lookup) are now logged at debug
level.