• El mundo es distinto ahora, pero los errores son los de siempre - Daniel Cantos Pardo
  • Era el primer viaje que realizaban sin tutor y saboreaban la libertad que con esa excitación que produce todo lo nuevo - Pablo Gonz
  • La falta de créditos retardó en tres años la partida de una verdadera expedición solarista - Stanislav Lem
  • El futuro ya está aquí, sólo que desigualmente repartido - W. Gibson
  • Me sentí como un punk que hubiera salido a comprar una navaja automática y volviera a casa con una pequeña bomba de neutrones - W. Gibson
  • A la mañana siguiente, realizaron su primer anochecer estelar - Diane Duane
  • —¿Un sol azul? —dijo Karellen, no muchas horas más tarde—. La identificación no puede ser muy difícil - Arthur C. Clarke
  • Aun así, en ese brillante interior había un núcleo oscuro, un indicio de algo encapsulado - Alastair Reynolds
  • El cielo sobre el puerto tenía el color de una pantalla de televisor sintonizado en un canal muerto - W. Gibson
  • Hace frío señor, en este campo —dijo el señor Tagomi—. Podemos regresar al centro de la ciudad en el helicóptero de la Misión, ¿le parece correcto? - Philip K. Dik
  • ¿Que es el ciberespacio? - El mundo - W. Gibson
  • Tengo sus anotaciones, estaban en su escritorio - Philip K. Dik
  • Esta formación constituye, en su totalidad, un desarrollo tridimensional de algún tipo de ecuación de orden superior - Stanislaw Lem
  • De nuevo la mezcla de rojo y verde, mirándole desde la naturaleza - Kim Stanley Robinson
  • Había un lugar en el Nostromo donde Dallas ocasionalmente encontraba algunos momentos de completa intimidad y al mismo tiempo se sentía razonablemente seguro. Era como una matriz artificial - Alan Dean Foster

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

Entrada escrita por: Fernando Lanero Barbero
[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

Entrada escrita por: Fernando Lanero Barbero
[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...

[ACTUALIZACIÓN] #ARCHLINUX. Bugtracker migration to GitLab completed

Entrada escrita por: Fernando Lanero Barbero
[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/bugtracker-migration-to-gitlab-completed/) Bugtracker migration to GitLab completed
Dec 4th 2023, 00:01

We are happy to announce that the (https://lists.archlinux.org/hyperkitty/list/arch-dev-public@lists.archlinux.org/thread/WYXDTJ3TR2DWRQCDZK44BQDH67IDVGTS/) migration of the bugtracker to GitLab is done! 🥳
Thanks to everyone who has helped during the migration!
This means the issue tracker and merge requests on the GitLab package repos are now enabled.
The old bugtracker will subsequently be closed down. For archiving reasons there will be a static copy so that links (for example the randomly picked (https://bugs.archlinux.org/task/56716) Task #56716) are still stable, migrated bugs have a closing comment pointing to the new URL on GitLab.
Packaging bugs are now opened on the repo hosting the corresponding packaging sources, the "Add a new Bug" button on the package page on archlinux.org will automatically direct you to the correct place to open the issue. The workflow afterwards is mostly the same, first our (https://gitlab.archlinux.org/groups/archlinux/teams/bug-wranglers/-/group_members) Bug Wranglers will have a look at the issues and triage them, and then they will be handed over to the respective (https://gitlab.archlinux.org/archlinux/teams/package-maintainer-team) Package Maintainers to fix. A list of all issues can be found (https://gitlab.archlinux.org/groups/archlinux/packaging/-/issues) here.
If you do not have an account for GitLab already (which authenticates against our (https://accounts.archlinux.org/) SSO service), please write us a mail with your desired username to accountsupport@archlinux.org as advised in the banner.

 

https://archlinux.org/news/bugtracker-migration-to-gitlab-completed/

Toda la información y las últimas novedades relativas al software libre y a Ubuntu las puedes encontrar en (http://linuxleon.org) linuxleon.org y (http://ubuntuleon.com) ubuntuleon.com.

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed
Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. Incoming changes in JDK / JRE 21 packages may require manual intervention

Entrada escrita por: Fernando Lanero Barbero
[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/) Incoming changes in JDK / JRE 21 packages may require manual intervention
Nov 2nd 2023, 11:51

We are introducing a change in JDK/JRE packages of our distro. This is
triggered from the way a JRE is build in modern versions of Java (>9). We are
introducing this change in Java 21.
To sum it up instead of having JDK and JRE packages coexist in the same system
we will be making them conflict. The JDK variant package includes the runtime
environment to execute Java applications so if one needs compilation and
runtime of Java they need only the JDK package in the future. If, on the other
hand, they need just runtime of Java then JRE (or jre-headless) will work.
This will (potentially) require a manual user action during upgrade:

if you have both JDK and JRE installed you can manually install the JDK
with pacman -Sy jdk-openjdk and this removes the JRE related packages.
if you have both JRE and JRE-headless you will need to choose one of
them and install it manually since they would conflict each other now.
If you only have one of the JDK/JRE/JRE-headless pacman should resolve
dependencies normally and no action is needed.

At the moment this is only valid for the upcoming JDK 21 release.

 

https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/

Toda la información y las últimas novedades relativas al software libre y a Ubuntu las puedes encontrar en (http://linuxleon.org) linuxleon.org y (http://ubuntuleon.com) ubuntuleon.com.

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed
Leer más...

[ACTUALIZACIÓN] #ARCHLINUX. Changes to default password hashing algorithm and umask settings

Entrada escrita por: Fernando Lanero Barbero
[ACTUALIZACIÓN] #ARCHLINUX

The latest and greatest news from the Arch Linux distribution.

(https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/) Changes to default password hashing algorithm and umask settings
Sep 22nd 2023, 22:26

With shadow >= 4.14.0, Arch Linux's default password hashing algorithm changed from SHA512 to yescrypt [1].
Furthermore, the umask [2] settings are now configured in /etc/login.defs instead of /etc/profile.
This should not require any manual intervention.
Reasons for Yescrypt
The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam [3]) and its stronger resilience towards password cracking attempts over SHA512.
Although the winner of the Password Hashing Competition [4] has been argon2, this even more resilient algorithm is not yet available in libxcrypt [5][6].
Configuring yescrypt
The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value [7]. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix [8] module (i.e. in /etc/pam.d/system-auth).
General list of changes

yescrypt is used as default password hashing algorithm, instead of SHA512

pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile

[1] https://www.openwall.com/yescrypt/
[2] https://man.archlinux.org/man/umask.1p
[3] https://wiki.archlinux.org/title/PAM
[4] https://www.password-hashing.net/
[5] https://github.com/besser82/libxcrypt/pull/113
[6] https://github.com/besser82/libxcrypt/pull/150
[7] https://github.com/linux-pam/linux-pam/issues/607
[8] https://man.archlinux.org/man/pam_unix.8

 

https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/

Toda la información y las últimas novedades relativas al software libre y a Ubuntu las puedes encontrar en (http://linuxleon.org) linuxleon.org y (http://ubuntuleon.com) ubuntuleon.com.

(https://blogtrottr.com/unsubscribe/nx2/dCCZZN) unsubscribe from this feed
Leer más...