Re: non-critical security bug fix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Serge (what a nice name!  ;-) ),

Let me give you an example where we found this patch very useful.

A 3rd party library that we bought implemented a user-level SCTP protocol by opening raw sockets. This required our application to run as root. However, we didn't want for it to run as root, and wanted to set the CAP_NET_RAW option and have the interaction with the raw socket survive after when we switch the effective user away from root.

When reading "man capabilities" we found:

"If a process that has a 0 value for one or more of its user IDs wants to prevent its permitted capability set being cleared when it resets all of its user IDs to non-zero values, it can do so using the prctl() PR_SET_KEEPCAPS operation."

Correct me if I am wrong, but I believe that this sentence says just what I described above. If so, the previously attached patch has the behavior described in the man page.

Regards,

--
Serge Aleynikov
Routing R&D, IDT Telecom
Tel: +1 (973) 438-3436
Fax: +1 (973) 438-1464


Serge E. Hallyn wrote:
Quoting Serge Aleynikov ([email protected]):
To Maintainers of the linux/security/commoncap.c:

Patch description:
==================
This bug-fix ensures that if a process with root access sets keep_capabilities flag, current capabilities get preserved when the process switches from root to another effective user. It looks like this was intended from the way capabilities are documented, but the current->keep_capabilities flag is not being checked.

Note that without your patch, the permitted set is maintained, so that
you can regain the caps into your effective set after setuid if you
need.  i.e.

	prctl(PR_SET_KEEPCAPS, 1);
	setresuid(1000, 1000, 1000);
	caps = cap_from_text("cap_net_admin,cap_sys_admin,cap_dac_override=ep");
	ret = cap_set_proc(caps);

So this patch will change the default behavior, but does not add
features or change what is possible.

Ordinarely I'd say changing default behavior wrt security is a bad
thing, but given that this is "default behavior when doing prctl(PR_SET_KEEPCAPS)",
I don't know how much it matters.

Still, I like the current behavior, where setuid means drop effective
caps no matter what.

-serge




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux