What are the possible consequences of removing the package udisks2
from an Ubuntu server?
To me, this is safe as long as you do not need any particular mount-point, for example relying on GUI (involving D-bus) or encrypted filesystems with LUKS.
https://www.freedesktop.org/wiki/Software/udisks/
https://github.com/storaged-project/udisks
Simulation:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libatasmart4 libblockdev-crypto2 libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2
libnl-route-3-200 libparted-fs-resize0 libudisks2-0 libvolume-key1
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
udisks2
0 upgraded, 0 newly installed, 1 to remove and 88 not upgraded.
After this operation, 1204 kB disk space will be freed.
Do you want to continue? [Y/n]
Package info:
Package: udisks2
Version: 2.9.4-1ubuntu2
Priority: optional
Section: admin
Origin: Ubuntu
Maintainer: Ubuntu Developers <[email protected]>
Original-Maintainer: Utopia Maintenance Team <[email protected]>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1204 kB
Depends: dbus, libblockdev-fs2, libblockdev-loop2, libblockdev-part2, libblockdev-swap2, parted, udev, libacl1 (>= 2.2.23), libatasmart4 (>= 0.13), libblockdev-utils2 (>= 2.24), libblockdev2 (>= 2.25), libc6 (>= 2.34), libglib2.0-0 (>= 2.50), libgudev-1.0-0 (>= 165), libmount1 (>= 2.30), libpolkit-agent-1-0 (>= 0.102), libpolkit-gobject-1-0 (>= 0.102), libsystemd0 (>= 209), libudisks2-0 (>= 2.9.0), libuuid1 (>= 2.16)
Recommends: dosfstools, e2fsprogs, eject, libblockdev-crypto2, ntfs-3g, policykit-1, libpam-systemd
Suggests: btrfs-progs, f2fs-tools, libblockdev-mdraid2, mdadm, nilfs-tools, reiserfsprogs, udftools, udisks2-bcache, udisks2-btrfs, udisks2-lvm2, udisks2-zram, xfsprogs, exfatprogs
Homepage: https://www.freedesktop.org/wiki/Software/udisks
Task: ubuntu-desktop-minimal, ubuntu-desktop, cloud-image, ubuntu-desktop-raspi, server, ubuntu-server-raspi, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi
Download-Size: 285 kB
APT-Manual-Installed: no
APT-Sources: http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Description: D-Bus service to access and manipulate storage devices
The udisks daemon serves as an interface to system block devices,
implemented via D-Bus. It handles operations such as querying, mounting,
unmounting, formatting, or detaching storage devices such as hard disks
or USB thumb drives.
.
This package also provides the udisksctl utility, which can be used to
trigger these operations from the command line (if permitted by
PolicyKit).
.
Creating or modifying file systems such as XFS, RAID, or LUKS encryption
requires that the corresponding mkfs.* and admin tools are installed, such as
dosfstools for VFAT, xfsprogs for XFS, or cryptsetup for LUKS.
There are some good reasons to try to do that. For example, to reduce the entropy from an ITSec perspective. But also to save some KB of RAM. I have no particular use-case for this need, this is just my curiosity in Ubuntu. Usually I work in minimal Debian servers and I don't see that daemon running there.
I ask this, since I'm curious about the possible consequences. Also because sometime it's not possible to create a virtual machine to test this kind of things, especially if you are working on a legacy bare metal.
Thanks for your thoughts about this Ubuntu package.