On 2023-12-15 21:42, Nicolas FORMICHELLA wrote:
Dec 15, 2023 20:07:42 Martin Wilck via openSUSE Factory <factory@lists.opensuse.org>:
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow:
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted.
To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un-blacklist it for future use.
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems. The list is incomplete, because reiserfs is not listed, and it can not be mounted. The installation DVD refuses to upgrade a machine if it sees reiserfs in the fstab, even if it is a data partition. It must be an evil one, not even named, like Voldemort >:-)
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
Unless I am mistaken, ntfs3 kmod is needed to mount NTFS then why would we blacklist it?
Preventing anyone from reading/wrtiting Windows disks by default is honestly a lunar idea, especially if you want new users to onboard the distro from Windows
I would love to hear the reasoning about blacklisting that (considering we do not blacklist apfs for ex.)
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3 -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)