vfs: Allow chroot if you have CAP_SYS_CHROOT in your user namespace · a85fb273c9 - Gogs

vfs: Allow chroot if you have CAP_SYS_CHROOT in your user namespace

Once you are confined to a user namespace applications can not gain
privilege and escape the user namespace so there is no longer a reason
to restrict chroot.

Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

Eric W. Biederman 13 years ago

parent

50804fe373

commit

a85fb273c9

1 changed files with 1 additions and 1 deletions

Split View Show Diff Stats

						
							+ 1
							
							- 1
						
fs/open.c
							 
								View File
							
				@@ -435,7 +435,7 @@ SYSCALL_DEFINE1(chroot, const char __user *, filename)
			
				 		goto dput_and_out;
			
				 	error = -EPERM;
			
				-	if (!capable(CAP_SYS_CHROOT))
			
				+	if (!nsown_capable(CAP_SYS_CHROOT))
			
				 		goto dput_and_out;
			
				 	error = security_path_chroot(&path);
			
				 	if (error)