August 2025 - Arch-announce - lists.archlinux.org

Recent service outages
by gromit 22 Aug '25

22 Aug '25

We want to provide an update on the recent [service outages][0] affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums. We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards. To improve the communication around this issue we will provide regular updates on our [service status page](https://status.archlinux.org) going forward. As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues. Please bear with us and thank you for all the support you have shown so far. ## Workarounds during service disruption - In the case of downtime for archlinux.org: - **Mirrors**: The mirror list endpoint used in tools like `reflector` is hosted on this site. Please default to the mirrors listed in the `pacman-mirrorlist` package during an outage. - **ISO**: Our installation image is available on a lot of the mirrors, for example the DevOps administered [geomirrors][1]. Please always verify its integrity as [described on the wiki][2] and confirm it is signed by `0x54449A5C` (or other trusted keys that may be used in the future). - In the case of downtime for aur.archlinux.org: - **Packages**: We maintain a [mirror of AUR packages][3] on GitHub. You can retrieve a package using: `$ git clone --branch <package_name> --single-branch https://github.com/archlinux/aur.git <package_name>` ## Additional remarks - Our services may send an initial connection reset due to the TCP SYN authentication performed by our hosting provider, but subsequent requests should work as expected. - We are keeping technical details about the attack, its origin and our mitigation tactics internal while the attack is still ongoing. [0]: https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/… [1]: https://geo.mirror.pkgbuild.com/iso/ [2]: https://wiki.archlinux.org/title/Installation_guide#Verify_signature [3]: https://github.com/archlinux/aur

1 0

[arch-announce] Recent services outages
by Arch Linux: Recent news updates: Christian Heusel 21 Aug '25

21 Aug '25

We want to provide an update on the recent [service outages][0] affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums. We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards. To improve the communication around this issue we will provide regular updates on our [service status page](https://status.archlinux.org) going forward. As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues. Please bear with us and thank you for all the support you have shown so far. ## Workarounds during service disruption - In the case of downtime for archlinux.org: - **Mirrors**: The mirror list endpoint used in tools like `reflector` is hosted on this site. Please default to the mirrors listed in the `pacman-mirrorlist` package during an outage. - **ISO**: Our installation image is available on a lot of the mirrors, for example the DevOps administered [geomirrors][1]. Please always verify its integrity as [described on the wiki][2] and confirm it is signed by `0x54449A5C` (or other trusted keys that may be used in the future). - In the case of downtime for aur.archlinux.org: - **Packages**: We maintain a [mirror of AUR packages][3] on GitHub. You can retrieve a package using: `$ git clone --branch <package_name> --single-branch https://github.com/archlinux/aur.git <package_name>` ## Additional remarks - Our services may send an initial connection reset due to the TCP SYN authentication performed by our hosting provider, but subsequent requests should work as expected. - We are keeping technical details about the attack, its origin and our mitigation tactics internal while the attack is still ongoing. [0]: https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/… [1]: https://geo.mirror.pkgbuild.com/iso/ [2]: https://wiki.archlinux.org/title/Installation_guide#Verify_signature [3]: https://github.com/archlinux/aur URL: https://archlinux.org/news/recent-services-outages/

1 0

[arch-announce] zabbix >= 7.4.1-2 may requires manual intervention
by Arch Linux: Recent news updates: Robin Candau 04 Aug '25

04 Aug '25

Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally [intended by upstream](https://www.zabbix.com/documentation/current/en/manual/installati… and done by other distributions): - zabbix-server - zabbix-proxy - zabbix-agent *(also used by the `zabbix-agent2` package)* - zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` *split* package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: - `PSK` files used for encrypted communication - Custom scripts for metrics collections or report generations - `sudoers` rules for metrics requiring elevated privileges to be collected - ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may [remove the obsolete user accounts from your system](https://wiki.archlinux.org/title/Users_and_groups#Other_examples_of…. URL: https://archlinux.org/news/zabbix-741-2-may-requires-manual-intervention/

1 0