Aggregator

• python-nh3-0.3.7-2.fc44
• rust-ammonia-4.1.8-1.fc44

Update the ammonia crate to version 4.1.8. Rebuild python-nh3 to apply security fixes (RUSTSEC-2021-0156, RUSTSEC-2021-0158, RUSTSEC-2026-0373).

• python-nh3-0.3.7-2.fc45
• rust-ammonia-4.1.8-1.fc45

Update the ammonia crate to version 4.1.8. Rebuild python-nh3 to apply security fixes (RUSTSEC-2021-0156, RUSTSEC-2021-0158, RUSTSEC-2026-0373).

• python-nh3-0.3.7-2.fc46
• rust-ammonia-4.1.8-1.fc46

Update the ammonia crate to version 4.1.8. Rebuild python-nh3 to apply security fixes (RUSTSEC-2021-0156, RUSTSEC-2021-0158, RUSTSEC-2026-0373).

• rust-resctl-bench-2.2.5-15.el9

Rebuilt with updated webpki dependencies

• Fixes RUSTSEC-2026-0381, RUSTSEC-2026-0383, and RUSTSEC-2026-0382.

Fix compilation error with recent versions of Rust and / or package dependencies. Fixes FTBFS issues across all currently supported branches of Fedora and on EPEL 9.

• openssh-10.0p1-14.fc43

Fix CVE-2026-106585: Denial of service via oversized decompressed packets

• rustup-1.29.0-9.fc43

Rebuilt with rustls v0.23.46

• Fixes RUSTSEC-2026-0346, RUSTSEC-2026-0347, RUSTSEC-2026-0348, and RUSTSEC-2026-0349.

• rust-resctl-bench-2.2.5-15.fc43

Rebuilt with updated webpki dependencies

• Fixes RUSTSEC-2026-0381, RUSTSEC-2026-0383, and RUSTSEC-2026-0382.

Fix compilation error with recent versions of Rust and / or package dependencies. Fixes FTBFS issues across all currently supported branches of Fedora and on EPEL 9.

• rust-cargo-deny-0.19.9-3.fc43

Rebuilt with updated webpki dependencies

• Fixes RUSTSEC-2026-0381, RUSTSEC-2026-0383, and RUSTSEC-2026-0382.

• atuin-18.12.1-5.el10_4

Rebuilt with updated rustls and webpki dependencies, including updated CA certificates for the eMudhra intermediate CA compromise.

• rust-resctl-bench-2.2.5-15.fc44

Rebuilt with updated webpki dependencies

• Fixes RUSTSEC-2026-0381, RUSTSEC-2026-0383, and RUSTSEC-2026-0382.

Fix compilation error with recent versions of Rust and / or package dependencies. Fixes FTBFS issues across all currently supported branches of Fedora and on EPEL 9.

• rustup-1.29.0-9.fc44

Rebuilt with rustls v0.23.46

• Fixes RUSTSEC-2026-0346, RUSTSEC-2026-0347, RUSTSEC-2026-0348, and RUSTSEC-2026-0349.

• openssh-10.2p1-16.fc44

Fix CVE-2026-106585: Denial of service via oversized decompressed packets

• btrfs-backup-ng-0.9.18-2.fc43

notes=Update to 0.9.18, which carries the 0.9.17 security fix (GHSA-5xvm-66c9-p5ph) and a fix for a regression in 0.9.17. 0.9.17 was not shipped to this release.

Security: the lock store created directories, wrote holder records and read them back with operations that followed a symbolic link. If the lock-store directory on a backup location was writable by another local account, a planted symlink could redirect those writes and reads; with a backup run as root, as a scheduled backup usually is, that let a less privileged local user steer a root write or read. Locally the lock store now works on O_NOFOLLOW file descriptors, and over ssh each directory component is created with a plain mkdir, records are written under set -C, and a record that is a link or not a regular file is refused.

Breaking: a lock-store directory writable by its group or by everyone is now refused with an error naming the directory and the remedy (chmod go-w <path>). A store created by an earlier version under an interactive umask 002 is mode 0775 and will be refused until tightened; stores created by a root timer or over ssh are 0755 and unaffected. New stores are created 0755 regardless of umask.

0.9.18 fixes the 0.9.17 regression where every exclusive lock on a local btrfs destination on kernel 6.6 or newer failed with "remote lock ... is busy", so a receive or prune into a local btrfs location could not run.

This update includes all changes since 0.9.16.

Advisory: https://github.com/berrym/btrfs-backup-ng/security/advisories/GHSA-5xvm-66c9-p5ph Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.18/CHANGELOG.md

Update to 0.9.16.

• A source could keep a snapshot forever and send it again in full on every run; fixed on the first run after upgrading.
• On a root-owned destination with ssh_sudo, locks went stale while a transfer was still running; the heartbeat now elevates like the acquire (expect one "sudo -n sh -c" per beat in the sudo log).
• restore --unlock no longer erases a pin a running restore has just taken.
• doctor reports who holds each pin, and --fix repairs only what it can prove is stale.

A .btrfs-backup-ng.locks.holders directory now appears beside each lock file; it is runtime state, and older versions ignore it.

This update includes all changes since 0.9.12.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.16/CHANGELOG.md

Update to 0.9.15.

• Pins on the source could be lost or left behind when several targets sent in parallel; fixed.
• A compressed ssh:// backup to a remote without the decompressor is refused before the transfer starts, instead of failing after the stream has been sent.
• estimate exits 2 when it could not measure and 3 when the destination is short of space (it exited 0), and can now measure an ssh:// source.
• Pins on the source could be lost or left behind when several targets sent in parallel; fixed. Backups on the targets were not affected

This update includes all changes since 0.9.12, including 0.9.13's fixes for systems without sudo, openssl or bash as sh.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.15/CHANGELOG.md

Update to 0.9.14.

Fixes the test suite failing at startup with pytest older than 8.4 (upstream #121). There are no changes to the program itself. 0.9.14 also includes all of 0.9.13's fixes.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.14/CHANGELOG.md

Update to 0.9.13.

This release fixes failures on systems without the usual privileges or tools:

• A compressed backup to an ssh:// target whose remote sh is dash 0.5.13.0-0.5.13.4 failed. Nothing was written, and existing backups are not affected.
• A machine without sudo failed with "No such file or directory: 'sudo'". It now says what is needed; run stops at startup and doctor reports it.
• Size estimates failed when sudo refused or was missing, although the snapshot was readable. du is now retried as the user.
• A restore without openssl reported a missing passphrase instead of the missing program.

Changes you may notice after upgrading:

• config validate and doctor now check the snapper configuration and snapshot_dir that run depends on, so they can report an error for a configuration they accepted before.
• A space check based on a du figure (an upper bound) warns and proceeds instead of refusing.
• A sudo password containing a line break is refused with a message saying why.
• doctor has a new local_privilege check.

Packaging: the package now requires lzop (the program used for lzo compression) instead of the lzo library, and the build runs the full test suite, including the compression tests.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.13/CHANGELOG.md

Update to 0.9.12

• btrfs-backup-ng-0.9.18-1.fc44

notes=Update to 0.9.18, which carries the 0.9.17 security fix (GHSA-5xvm-66c9-p5ph) and a fix for a regression in 0.9.17. 0.9.17 was not shipped to this release.

Security: the lock store created directories, wrote holder records and read them back with operations that followed a symbolic link. If the lock-store directory on a backup location was writable by another local account, a planted symlink could redirect those writes and reads; with a backup run as root, as a scheduled backup usually is, that let a less privileged local user steer a root write or read. Locally the lock store now works on O_NOFOLLOW file descriptors, and over ssh each directory component is created with a plain mkdir, records are written under set -C, and a record that is a link or not a regular file is refused.

Breaking: a lock-store directory writable by its group or by everyone is now refused with an error naming the directory and the remedy (chmod go-w <path>). A store created by an earlier version under an interactive umask 002 is mode 0775 and will be refused until tightened; stores created by a root timer or over ssh are 0755 and unaffected. New stores are created 0755 regardless of umask.

0.9.18 fixes the 0.9.17 regression where every exclusive lock on a local btrfs destination on kernel 6.6 or newer failed with "remote lock ... is busy", so a receive or prune into a local btrfs location could not run.

This update includes all changes since 0.9.16.

Advisory: https://github.com/berrym/btrfs-backup-ng/security/advisories/GHSA-5xvm-66c9-p5ph Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.18/CHANGELOG.md

• btrfs-backup-ng-0.9.18-1.fc45

notes=Update to 0.9.18, which carries the 0.9.17 security fix (GHSA-5xvm-66c9-p5ph) and a fix for a regression in 0.9.17. 0.9.17 was not shipped to this release.

Security: the lock store created directories, wrote holder records and read them back with operations that followed a symbolic link. If the lock-store directory on a backup location was writable by another local account, a planted symlink could redirect those writes and reads; with a backup run as root, as a scheduled backup usually is, that let a less privileged local user steer a root write or read. Locally the lock store now works on O_NOFOLLOW file descriptors, and over ssh each directory component is created with a plain mkdir, records are written under set -C, and a record that is a link or not a regular file is refused.

Breaking: a lock-store directory writable by its group or by everyone is now refused with an error naming the directory and the remedy (chmod go-w <path>). A store created by an earlier version under an interactive umask 002 is mode 0775 and will be refused until tightened; stores created by a root timer or over ssh are 0755 and unaffected. New stores are created 0755 regardless of umask.

0.9.18 fixes the 0.9.17 regression where every exclusive lock on a local btrfs destination on kernel 6.6 or newer failed with "remote lock ... is busy", so a receive or prune into a local btrfs location could not run.

This update includes all changes since 0.9.16.

Advisory: https://github.com/berrym/btrfs-backup-ng/security/advisories/GHSA-5xvm-66c9-p5ph Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.18/CHANGELOG.md

Update to 0.9.16.

• A source could keep a snapshot forever and send it again in full on every run; fixed on the first run after upgrading.
• On a root-owned destination with ssh_sudo, locks went stale while a transfer was still running; the heartbeat now elevates like the acquire (expect one "sudo -n sh -c" per beat in the sudo log).
• restore --unlock no longer erases a pin a running restore has just taken.
• doctor reports who holds each pin, and --fix repairs only what it can prove is stale.

A .btrfs-backup-ng.locks.holders directory now appears beside each lock file; it is runtime state, and older versions ignore it.

This update includes all changes since 0.9.12.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.16/CHANGELOG.md

Update to 0.9.15.

• Pins on the source could be lost or left behind when several targets sent in parallel; fixed.
• A compressed ssh:// backup to a remote without the decompressor is refused before the transfer starts, instead of failing after the stream has been sent.
• estimate exits 2 when it could not measure and 3 when the destination is short of space (it exited 0), and can now measure an ssh:// source.
• Pins on the source could be lost or left behind when several targets sent in parallel; fixed. Backups on the targets were not affected

This update includes all changes since 0.9.12, including 0.9.13's fixes for systems without sudo, openssl or bash as sh.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.15/CHANGELOG.md

Update to 0.9.14.

Fixes the test suite failing at startup with pytest older than 8.4 (upstream #121). There are no changes to the program itself. 0.9.14 also includes all of 0.9.13's fixes.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.14/CHANGELOG.md

Update to 0.9.13.

This release fixes failures on systems without the usual privileges or tools:

• A compressed backup to an ssh:// target whose remote sh is dash 0.5.13.0-0.5.13.4 failed. Nothing was written, and existing backups are not affected.
• A machine without sudo failed with "No such file or directory: 'sudo'". It now says what is needed; run stops at startup and doctor reports it.
• Size estimates failed when sudo refused or was missing, although the snapshot was readable. du is now retried as the user.
• A restore without openssl reported a missing passphrase instead of the missing program.

Changes you may notice after upgrading:

• config validate and doctor now check the snapper configuration and snapshot_dir that run depends on, so they can report an error for a configuration they accepted before.
• A space check based on a du figure (an upper bound) warns and proceeds instead of refusing.
• A sudo password containing a line break is refused with a message saying why.
• doctor has a new local_privilege check.

Packaging: the package now requires lzop (the program used for lzo compression) instead of the lzo library, and the build runs the full test suite, including the compression tests.

Full changelog: https://github.com/berrym/btrfs-backup-ng/blob/v0.9.13/CHANGELOG.md

Update to 0.9.12

• util-linux-2.41.6-1.fc43

Upgrade to upstream release v2.41.6 with security-related patches.

• rust-cargo-deny-0.19.9-3.fc44

Rebuilt with updated webpki dependencies

• Fixes RUSTSEC-2026-0381, RUSTSEC-2026-0383, and RUSTSEC-2026-0382.

• util-linux-2.41.6-1.fc44

Upgrade to upstream release v2.41.6 for security-related changes.

• atuin-18.12.1-5.fc43

Rebuilt with updated rustls and webpki dependencies, including updated CA certificates for the eMudhra intermediate CA compromise.