[ACTUALIZACIÓN] #ARCHLINUX. Arch Linux 2024 Leader Election Results

[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/arch-linux-2024-leader-election-results/) Arch Linux 2024 Leader Election Results
Apr 15th 2024, 08:56

Recently we held our leader election, and the previous Project Leader Levente "anthraxx" Polyák ran again while no other people were nominated for the role.
As per (https://wiki.archlinux.org/title/DeveloperWiki:Project_Leader#Election) our election rules he is re-elected for a new term.
The role of of the project lead within Arch Linux is connected to (https://wiki.archlinux.org/title/DeveloperWiki:Project_Leader#Roles) a few
responsibilities regarding decision making (when no consensus can be reached), handling
financial matters with SPI and overall project management tasks.
Congratulations to Levente and all the best wishes for another successful term! 🥳

 

https://archlinux.org/news/arch-linux-2024-leader-election-results/

Toda la información y las últimas novedades del software libre las puedes encontrar en (http://ubuntuleon.com) ubuntuleon.com

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed

 

Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. Increasing the default vm.max_map_count value

[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/) Increasing the default vm.max_map_count value
Apr 7th 2024, 20:12

The (https://docs.kernel.org/admin-guide/sysctl/vm.html#max-map-count) vm.max_map_count paramater will be increased from the default 65530 value to 1048576.
This change should help address performance, crash or start-up issues for a number of memory intensive applications, particularly for (but not limited to) (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057792/comments/5) some Windows games played through Wine/Steam Proton. Overall, end users should have a smoother experience out of the box with no expressed concerns about potential downsides in (https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/) the related proposal on arch-dev-public mailing list.
This vm.max_map_count increase is introduced in the 2024.04.07-1 release of the (https://archlinux.org/packages/core/any/filesystem/) filesystem package and will be effective right after the upgrade.
Before upgrading, in case you are already setting your own value for that parameter in a sysctl.d configuration file, either remove it (to switch to the new default value) or make sure your configuration file will be read (https://man.archlinux.org/man/sysctl.8#SYSTEM_FILE_PRECEDENCE) with a higher priority than the /usr/lib/sysctl.d/10-arch.conf file (to supersede the new default value).

 

https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/

Toda la información y las últimas novedades del software libre las puedes encontrar en (http://ubuntuleon.com) ubuntuleon.com

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed

 

Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. The xz package has been backdoored

[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/the-xz-package-has-been-backdoored/) The xz package has been backdoored
Mar 29th 2024, 19:55

TL;DR: Upgrade your systems and container images now!
As many of you may have already read (https://www.openwall.com/lists/oss-security/2024/03/29/4) 1, the upstream release tarballs for xz in version 5.6.0 and 5.6.1 contain malicious code which adds a backdoor.
This vulnerability is tracked in the Arch Linux security tracker (https://security.archlinux.org/ASA-202403-1) 2.
The xz packages prior to version 5.6.1-2 (specifically 5.6.0-1 and 5.6.1-1) contain this backdoor.
The following release artifacts contain the compromised xz:

installation medium 2024.03.01

virtual machine images 20240301.218094 and 20240315.221711

container images created between and including 2024-02-24 and 2024-03-28

The affected release artifacts have been removed from our mirrors.
We strongly advise against using affected release artifacts and instead downloading what is currently available as latest version!
Upgrading the system
It is strongly advised to do a full system upgrade right away if your system currently has xz version 5.6.0-1 or 5.6.1-1 installed:
pacman -Syu
Upgrading container images
To figure out if you are using an affected container image, use either
podman image history archlinux/archlinux
or
docker image history archlinux/archlinux
depending on whether you use podman or docker.
Any Arch Linux container image older than 2024-03-29 and younger than 2024-02-24 is affected.
Run either
podman image pull archlinux/archlinux
or
docker image pull archlinux/archlinux
to upgrade affected container images to the most recent version.
Afterwards make sure to rebuild any container images based on the affected versions and also inspect any running containers!
Regarding sshd authentication bypass/code execution
From the upstream report (https://www.openwall.com/lists/oss-security/2024/03/29/4) 1:

openssh does not directly use liblzma. However debian and several other
distributions patch openssh to support systemd notification, and libsystemd
does depend on lzma.

Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command:
ldd "$(command -v sshd)"
However, out of an abundance of caution, we advise users to remove the malicious code from their system by upgrading either way. This is because other yet-to-be discovered methods to exploit the backdoor could exist.

 

https://archlinux.org/news/the-xz-package-has-been-backdoored/

Toda la información y las últimas novedades del software libre las puedes encontrar en (http://ubuntuleon.com) ubuntuleon.com

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed

 

Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. mkinitcpio hook migration and early microcode

[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/mkinitcpio-hook-migration-and-early-microcode/) mkinitcpio hook migration and early microcode
Mar 4th 2024, 18:14

With the release of (https://lists.archlinux.org/hyperkitty/list/arch-projects@lists.archlinux.org/thread/PZHWLVJLN5EPW6EVK2HEKVBDBNZWHREN/) mkinitcpio v38, several hooks previously provided by Arch packages have been
moved to the mkinitcpio upstream project. The hooks are: systemd, udev, encrypt,
sd-encrypt, lvm2 and mdadm_udev.
To ensure no breakage of users' setup occurs, temporary
conflicts have been introduced into the respective packages to prevent installing packages
that are no longer compatible.
The following packages needs to be upgraded together:

mkinitcpio 38-2
systemd 255.4-2
lvm2 2.03.23-3
mdadm 4.3-2
cryptsetup 2.7.0-3

Please note that the mkinitcpio flag --microcode, and the microcode option in the preset files, has been deprecated in favour of
a new microcode hook. This also allows you to drop the microcode initrd
lines from your boot configuration as they are now packed together with the main initramfs image.

 

https://archlinux.org/news/mkinitcpio-hook-migration-and-early-microcode/

Toda la información y las últimas novedades del software libre las puedes encontrar en (http://ubuntuleon.com) ubuntuleon.com

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed

 

Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. Making dbus-broker our default D-Bus daemon

[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon/) Making dbus-broker our default D-Bus daemon
Jan 9th 2024, 17:59

We are making dbus-broker our default implementation of D-Bus, for
improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon,
the previous implementation. Pacman will ask you whether to install
dbus-broker-units or dbus-daemon-units. We recommend picking the
default.
For a more detailed rationale, please see our (https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0025-dbus-broker-default.rst) RFC 25.

 

https://archlinux.org/news/making-dbus-broker-our-default-d-bus-daemon/

Toda la información y las últimas novedades del software libre las puedes encontrar en (http://ubuntuleon.com) ubuntuleon.com

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed

 

Leer más...