Veracrypt, FreeBSD 13 and FuseFS: can’t load fuse
This is a short and simple post related to FreeBSD 13 and FuseFS. Chances are that when you’ll read this, the problem will be already fixed.TLDR: in the upgrading from FreeBSD 12 to FreeBSd 13 the fuse kernel module has been renamed to fusefs. The post-install instructions for Veracrypt, that is a program for encrypting FUSE disks, wrongly refer to the old module name.
What is the problem, thus?
When you install Veracrypt, that in turns depends on
fusefs-libs, you will get some post-install information like the following:
=====
Message from fusefs-libs-2.9.9_2:
--
Install the FUSE kernel module (kldload fusefs) to use this port.
=====
Message from veracrypt-1.24_4:
--
Veracrypt was installed
1) Veracrypt needs security/sudo port to mount disk volumes. You must modify
/usr/local/etc/sudoers file to add Veracrypt user(s). Don't use root user
2) Please ensure that the fusefs kmod is loaded prior to use:
$ kldload fuse
If you want load fuse.ko on boot time, please add the following to /boot/loader.conf
fusefs_load="YES"
3) Enjoy it
At the point
2 there is the explicit instruction to load the kernal module via kldload fuse.
But the module is called fusefs since FreeBSD 13, therefore the right instruction is kldload fusefs.
It is also important to note that such instruction must be executed by a superuser, either
root or via sudo/doas.
I’ve posted this oddity to the FreeBSD forums in the hope to help the system to improve and be as much accurate as possible.
I’ve also submitted a bug. In the beginning, I mispelled the bug report, since I was mislead from the header of the above message and thought it was generated by
fusefs-libs, but reading than carefully, it was clearly a problem of veracrypt.