Red Hat Bugzilla – Bug 593635
Capabilities can't be set on just a thread
Last modified: 2010-07-02 15:22:45 EDT
Description of problem: When changing capabilities on a thread, it actually changes the capabilities for the process. Will attach reproducer.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
libcap-ng-0.6.4-1..el6 was built to solve this problem. libcap-ng0.6.4 only has 2 changes over the 0.6.2-5 package. When running on a system that has a program that is using a packet socket, it will now print the interface that its binding to. An example of this is if you have a system using dhclient rather than network manager, the dhcp process will show something like eth0 instead of 0.0.0.0. You can also try this with tcpdump and set the user to root so that it keeps capabilities. The other change fixes the bug mentioned above. I will attach a test program for that.
Created attachment 415135 [details] Test case This program can be used as a starting point for an automated test. On libcap-ng-0.6.2, you should see a "failed" message. On libcap-ng-0.6.4, you should not. Below is the Makefile that goes with this test case. LIBS= -lcap-ng -lpthread all: gcc -g pthread-cap-test.c -o pthread-cap-test $(LIBS) clean: rm -f pthread-cap-test *.o
Built libcap-ng-0.6.4-2.el6 to address this problem and to add a requires %{name} = %{version}-%{release} to the utils subpackage.
Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.