Description of problem: The command: sandbox -X -t sandbox_web_t firefox Returns: execv: No such file or directory Variations of the command produce the same result: [default@localhost ~]$ mkdir /tmp/myweb ~/myweb [default@localhost ~]$ sandbox -X -T /tmp/myweb -H ~/myweb -t sandbox_web_t firefox danwalsh.livejournal.com execv: No such file or directory Version-Release number of selected component (if applicable): Fedora 13 /usr/bin/sandbox How reproducible: Always Steps to Reproduce: 1. Install a fresh copy of Fedora 13 x86_64 2. Open terminal as normal user and execute "sandbox -X -t sandbox_web_t firefox" Actual results: execv: No such file or directory Expected results: Firefox launches in a sadboxed enviroment Additional info:
Are you seeing AVC messages?
No, and if I launch the SELinux Troubleshooter it is empty "No alerts to view".
Have you rebooted the machine after the install? Have you udpated to the latest packages. sandbox -X requires that the file system be set up for namespacing. Unfortunately this requires a start up script /etc/init.d/sandbox to be run at boot time
Yes I rebooted, and completed "yup update". Starting /etc/init.d/sandbox had no effect: [default@localhost ~]$ su Password: [root@localhost default]# /etc/init.d/sandbox start [root@localhost default]# sandbox -X -t sandbox_web_t firefox Must not be root [root@localhost default]# exit exit [default@localhost ~]$ sandbox -X -t sandbox_web_t firefox execv: No such file or directory [default@localhost ~]$
What is the path to your homedir?
[default@localhost ~]$ readlink -f ~ /home/default
Does this mean that your homedir is not /home/default but some symbolic link that points at /home/default?
No, my homedir really is /home/default [default@localhost ~]$ ls /home default [default@localhost ~]$
And the entry in /etc/passwd says /home/default? sandbox is attempting to mount a file system over the existing $HOME and /tmp If these point somewhere else, it could be a problem. What happens when you run. seunshare -t /tmp/myweb -h ~/myweb -Z `id -Z` -- /usr/bin/id -Z
Yes, [default@localhost ~]$ cat /etc/passwd | grep default default:x:500:500::/home/default:/bin/bash [default@localhost ~]$ seunshare -t /tmp/myweb -h ~/myweb -Z `id -Z` -- /usr/bin/id -Z unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [default@localhost ~]$ ls -alh /tmp/myweb/ /home/default/myweb/ /home/default/myweb/: total 28K drwxrwxr-x. 2 default default 4.0K Jul 26 12:22 . drwx--x---+ 40 default users 4.0K Jul 28 08:37 .. -rwx------. 1 default default 269 Jul 26 12:22 .sandboxrc -rw-rw-r--. 1 default default 9.2K Jul 26 12:22 .xmodmap /tmp/myweb/: total 8.0K drwxrwxr-x. 2 default default 4.0K Jul 26 12:21 . drwxrwxrwt. 21 root root 4.0K Jul 28 09:39 ..
Does sandbox -X xterm Work?
Justin if you have access to IRC, ping dwalsh on freenode - #selinux
after installing xterm: [default@localhost ~]$ sandbox -X xterm execv: No such file or directory
Re: freenode, in #selinux now nick jakeogh
Is policycoreutils-sandbox installed?
No it was not. Installing that fixed the problem. Now: sandbox -X -t sandbox_web_t firefox works. Sorry if I missed the documentation that this had to be installed. Thanks! -Justin
Well that is actually a bug. It should tell you to install the package. I did not know this was happening until I tried it myself.
Miroslav we need to add execstack to sandbox_xserver_t
Fixed in selinux-policy-3.7.19-43.fc13.noarch.
selinux-policy-3.7.19-44.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/selinux-policy-3.7.19-44.fc13
selinux-policy-3.7.19-44.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/selinux-policy-3.7.19-44.fc13
selinux-policy-3.7.19-44.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.