Message-ID: <4B222C3D.2070807@icdsoft.com>
Date: Fri, 11 Dec 2009 13:25:49 +0200
From: Ivan Zahariev <famzah@icdsoft.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
CC: Ivan Zahariev <famzah@icdsoft.com>
Subject: EUID != root + EGID = root, and CAP_SETGID
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1193
Lines: 30

Hi guys,

Currently, if a process is started with EUID which is non-root, and EGID 
which IS root (for example by set-group-ID file permission + file group 
owner "root", or an account in /etc/passwd with group=0), then the 
processes is not granted CAP_SETGID.

As a result, such a process cannot change its EGID to an arbitrary one, 
even though the current EGID is the super-user "root" one. Therefore, 
such a process cannot easily drop its EGID "root" privileges to non-root 
ones, for security reasons.

This is not the case if the process starts with EUID=0. Then the 
processes is granted *both* CAP_SETUID and CAP_SETGID.

Is this an intended behavior? Shouldn't a process which is started with 
EGID=0 get CAP_SETGID too?

Thank you.

Best regads,
Ivan Zahariev

P.S. For more detailed info: 
http://blog.famzah.net/2009/12/11/linux-non-root-user-processes-which-run-with-group-root-cannot-change-their-process-group-to-an-arbitrary-one/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/