qqqq
May 28, 2025, 9:24pm
1
I have the same issue.
sf_name is the shared folder name
Steps to reproduce:
Followed the Kicksecure guide to setting up a shared folder to the letter (even folder name)
I am also getting the Permission denied
for any other action such as
sudo apt update
or other
Running Whonix XFCE workstation persistent mode version 17.3.9.9 on Ubuntu 25.04 with Virtualbox 7.0.20_Ubuntu
No help can be provided until a proper bug report has been posted.
This is a very different āissueā. You need to āfixā that first. Please do not mix that discussion into this topic. Please read:
Hello Iām brand new to Whonix, I installed a Ubuntu 24 LTS on my mini pc then added a Virtual Box.
The Gateway work and the terminal return something when I do a āsudo -lā but when using this same command on the Workstation I have āpermission denied : sudoā (no matter the sudo command)
Itās normal? So I canāt install anything with sudo on the Workstation? I canāt even do a āsudo apt update && sudo apt upgrade -yā
Thanks for any tips.
qqqq
May 28, 2025, 9:34pm
3
The bug report is that following to the letter the guide doesnāt work.
Step 1. Create folder on host named āsharedā
Step 2. Add it as a shared folder within Virtualbox UI
Step 3. Try to access it from Workstation
[workstation user ~]% cd /media/sf_shared
cd: permission denied: /media/sf_shared
zsh: exit 1
I included the other observation as I thought it might be relevant as itās also a permission issue.
1 Like
I moved this to its own forum thread because there is no mention of sf_name
in your issue report.
Failed to open directory āsf_nameā. Error opening directory ā/media/sf_nameā: Permission denied might be related or might be different.
For some reason, file permissions are no longer already prepared by vm-config-dist This might be a usablity bug, that will be investigated later and will likely be fixed in version 17.4.0.7
and above. (Unreleased at time of writing.)
But there is no need to wait for a fix. Users might be able to easily fix this.
Try this:
Shared Folder Permission Fix
(written just now)
qqqq
May 28, 2025, 10:51pm
5
Thanks for putting that together.
I actually managed to work around it.
I had to remove user-sysmaint-split
(using the splash screen option at boot).
As outlined in the wiki:
If using unrestricted admin mode: Not applicable.
Actually I was still getting the issue with unrestricted admin mode, I had to launch thunar with sudo perms: sudo thunar
and after transferring files to the user Desktop, I had to edit the permissions to be usable by user
.
If thereās a way to reinstall sysmain-split, Iāll gadly test your group configurations!
Only means the sysmaint notice isnāt applicable. Doesnāt mean to skip the rest of the instructions.
qqqq:
sudo thunar
Graphical Applications and Root Rights
sysmaint, Installation
qqqq
May 29, 2025, 8:08am
7
The guide you provided worked, adapting the commands (after installing sysmaint again):
sudo addgroup user vboxsf
throws an arg error
ended up using sudo usermod -a -G vboxsf user
and it works like a charm.
1 Like
Command has been corrected in the wiki. (Not using usermod but, see wiki.)