Darknet Girl - 2024-11-24

Hi!

My gut feeling is that this is not a bug and I'm possibly doing something wrong, but I can't understand what.
I'm running under FreeBSD 14.1 with veracrypt 1.26.15 installed from ports.

If I run veracrypt as a user, both GUI or text interface, and I try to mount a volume (with the correct volume and sudo passwords), I receive the message:
"Error: Not enough data available".

As an example, the command line is:
veracrypt --text --load-preferences --mount /home/darknetgirl/volume.dsk /home/darknetgirl/Documents/volume/ '--pim=0' '--keyfiles=' '--protect-hidden=no' '--slot=1'

If I run the above command with sudo, that works perfectly, ex:
sudo veracrypt --text --load-preferences --mount /home/darknetgirl/volume.dsk /home/darknetgirl/Documents/volume/ '--pim=0' '--keyfiles=' '--protect-hidden=no' '--slot=1'

veracrypt, under the hood, invoke sudo to process the actual mount command.

I used truss (trace in attach) and the command that fails seems to be:
sudo -S -p /usr/local/bin/veracrypt --core-service

With the following problem:
effective uid is not 0, is /usr/local/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?

I use ZFS, but the filesystem has setuid attribute activated by default

$ zfs get setuid zroot/usr
NAME       PROPERTY  VALUE   SOURCE
zroot/usr  setuid    on      default

And that is also confirmed by the fact I can run sudo in other contexts without problems.

What am I doing wrong?
Thanks!

 

Last edit: Darknet Girl 2024-11-24