{"id":184257,"date":"2026-11-14T17:41:15","date_gmt":"2026-11-14T15:41:15","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/vypusk-udisks-2-12-0-instrumentariya-dlya-upravleniya-diskami-v-linux"},"modified":"2026-11-14T17:41:27","modified_gmt":"2026-11-14T15:41:27","slug":"udisks-2-12-0-released-disk-management-tools-for-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/udisks-2-12-0-released-disk-management-tools-for-linux","title":{"rendered":"Release of UDisks 2.12.0, a toolkit for managing disks in Linux","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After two years of development, the release of UDisks 2.12.0 has been published, which includes a system background process, libraries, and tools for organizing access and managing disks, storage devices, and related technologies. UDisks provides a D-Bus API for working with disk partitions, configuring MD RAID, managing block devices in files (loop mounting), manipulating file systems, and more. Additionally, modules for monitoring and managing BTRFS, iSCSI, libStorageManagement, LVM2, and LVM Cache are included. For instance, UDisks is used in GNOME applications to work with disk partitions and in various graphical configuration tools.<\/p>\n
In the new version:<\/p>\n
\n
The command «udisksctl drive-set-standby» has been added to configure the timeout for putting the drive into sleep mode.\n
For setting up loop devices, authorization through PolKit (org.freedesktop.udisks2.loop-setup) is now always required.\n
In the API Filesystem.Mount(), the use of the «as-user» option is restricted; it now requires mandatory authorization using the actual user ID. This change was implemented following the recent fix for the vulnerability. \nCVE-2026-7867, which allowed unauthorized mounting operations on behalf of another user, including root, through manipulation of the ‘as-user’ option when making D-Bus calls to the Filesystem.Mount handler.<\/p>\n
Support for the 'discard' flag has been added in the API Encrypted.Unlock() and in \/etc\/crypttab, which enables the use of the TRIM command with encrypted partitions (by default not used, as it potentially allows for determining the distribution of free and occupied blocks on the disk).\n
In the API Encrypted.Unlock() and in \/etc\/crypttab, support for the «discard» flag has been added, which allows enabling the TRIM command for encrypted partitions (disabled by default as it may potentially reveal the distribution of free and occupied blocks on the disk).\n<\/ul>\n