Appliance DNS fix
VM images (OVA, qcow2, VHDX) kept the DNS server of the network they were built in. systemd-networkd receives DNS servers by DHCP but only passes them to systemd-resolved, which the appliance does not use, so /etc/resolv.conf was never updated. The appliance now writes the DNS servers of the DHCP lease — or the ones entered in the network settings, which take precedence — at every start, right after network changes and whenever the lease changes. New images contain no DNS servers. Appliances already installed are fixed by this update.
Other fixes
- File restores from VM backups: a read-only folder (for example
0555) got its permissions before its files were written, which failed unless the agent ran as root. - Email: the mail code itself refuses addresses with line breaks, also for a test message sent while email is switched off.
- Updated Go modules (x/crypto 0.58, x/sys, x/term, go-ldap, Azure SDK).
Repository
The repository now runs CI (tests on Linux, build for Windows), CodeQL, govulncheck, staticcheck, OpenSSF Scorecard and Dependabot on every change. SECURITY.md (github.com) lists how BackupZit is tested.
Update the console and then the agents (Agents → Update all).
Releases are signed with the BackupZit release key; consoles verify them before installing.
