Arch Linux changes default password hashing algorithm

Arch Linux

Arch Linux is a general-purpose Linux distribution aimed at advanced users.

A few days ago, it was announced through a post on the official Arch Linux website that the developers have changed the default password hash scheme, and that they have also changed the umask configuration.

The publication mentions that Arch Linux builds will now switch from using the SHA512 hash to using YesCrypt.

YesCrypt is a new scheme for encrypting passwords and generating cryptographic keys from passwords or passphrases. YesCrypt is based on scrypt and includes support for classic scrypt, a conservative modification of scrypt (called YESCRYPT_WORM), and finally, a deep modification of scrypt (called YESCRYPT_RW), which is offered as the main version (and is implicit in yescrypt from now on).

Among the advantages of Yescrypt, it is mentioned that it expands the capabilities of classic scrypt by supporting memory-intensive schemes and reducing the effectiveness of attacks using GPUs, FPGAs, and specialized chips. Yescrypt's security is ensured through the use of proven cryptographic primitives SHA-256, HMAC, and PBKDF2.

Yescrypt is the most scalable password hashing scheme, providing near-optimal security against offline attacks for a wide range of usable memory sizes, from kilobytes to terabytes and beyond. On the other hand, the cost of this is the complexity of yescrypt, and complexity is a disadvantage of any software.

For this reason, YesCrypt is currently intended for large deployments (millions of passwords) where YesCrypt's complexity is small compared to the overall complexity of the authentication service. For smaller deployments and program integrations, bcrypt remains a reasonable option in the short term for now.

On the other hand, the disadvantages of the previously used password hashing scheme based on the SHA512 algorithm include: the need to set sufficiently large salt values ​​(at least 128 bits), susceptibility to DoS attacks by creating parasitic load on the CPU when encoding long passwords, susceptibility to an attack that determines the password size based on passive analysis of the hash processing time, and working without using the cryptographic key derivation function (KDF).

Additionally, when using yescrypt, the umask configuration is now stored in the /etc/login.defs configuration file instead of /etc/profile.

Regarding the hash change, it is also mentioned that the Argon2 algorithm, which won the password hashing contest in 2015, was also considered as an option for password hashing, but it is not used in Arch Linux because it is not compatible with the libxcrypt library used in PAM.

In addition, speaking of improvements in Arch Linux, it's also worth highlighting the update to the Archinstall installer, version 2.6.1. Archinstall can be used instead of the distribution's default manual installation mode, providing a guided and automated installation experience.

In the new version the user now has the ability to configure an arbitrary number of parallel downloads, an option has been added to use ly as a console display manager and also use slick-greeter instead of gtk-greeter in lightdm. The kitty, Dolphin and wofi applications have been added to the profile that makes up the environment based on the Hyprland composite server.

Other notable changes in Archinstall 2.6.1 include:

  • Fixed crash caused by unsupported partitions
  • Fixed loading desktop profiles from preconfigured settings
  • Fixed GRUB installation issue on MBR devices due to incorrect target device
  • Fixed some bugs in manual partition
  • Fixed custom commands issue
  • Allow assigning mount points on existing partitions
  • Fix UUID acquisition
  • Sort profiles ignoring case

Finally, if you are interested in learning more about this , you can find the details at the following link.


Add as preferred source in Google