Arch-announce

Download

arch-announce@lists.archlinux.org

April 2026

1 participants
2 discussions

[arch-announce] kea >= 1:3.0.3-6 update requires manual intervention
by Arch Linux: Recent news updates: Robin Candau 07 Apr '26

07 Apr '26

The `kea` package has moved all services to run as a dedicated `kea` user (instead of `root`) for improved security. This change requires permission updates to the runtime files created by the `kea` services. Users upgrading from an existing `kea` installation should therefore run the following commands after the upgrade: `chown kea: /var/lib/kea/* /var/log/kea/* /run/lock/kea/logger_lockfile` `systemctl try-restart kea-ctrl-agent.service kea-dhcp{4,6,-ddns}.service` Accounts that need to interact with `kea` services files (e.g. lease files under `/var/lib/kea`, log files under `/var/log/kea` or configuration files under `/etc/kea`) should be added to the `kea` group. URL: https://archlinux.org/news/kea-1303-6-update-requires-manual-intervention/

1 0

[arch-announce] iptables now defaults to the nft backend
by Arch Linux: Recent news updates: Felix Yan 05 Apr '26

05 Apr '26

The old iptables-nft package name is replaced by iptables, and the legacy backend is available as iptables-legacy. When switching packages (among iptables-nft, iptables, iptables-legacy), check for .pacsave files in /etc/iptables/ and restore your rules if needed: - /etc/iptables/iptables.rules.pacsave - /etc/iptables/ip6tables.rules.pacsave Most setups should work unchanged, but users relying on uncommon xtables extensions or legacy-only behavior should test carefully and use iptables-legacy if required. URL: https://archlinux.org/news/iptables-now-defaults-to-the-nft-backend/

1 0