Skip to contentSkip to conversation

if (2.6.24.1 && capset && bind9) bug()

DISCUSSION Nick 'Zaf' Clifford 2 participants 3 messages Feb 11, 2008 – Feb 12, 2008 SELinux security module

lore
Share & tools
lore
#0 lore raw

Please CC me on any/all replies

After trying to upgrade to deal with the most recent security issue, I have encountered what has to either be me being very tired, or a kernel bug. After assuming that it was the former for 3 hours, I now conclude I'm more tired, and it has to be the latter.

Relevant versions:
Bind: 9.3.4
Kernel: Linux version 2.6.24.1.cerberus.1 (zaf@cerberus) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Mon Feb 11 20:05:58 NZDT 2008
Distro: Ubuntu Feisty
Processor: AMD Athlon

# cat /proc/cmdline
root=UUID=0996d997-a1f5-4601-964e-f3e71a477b81 ro quiet splash

Relevant .config settings (please let me know if more are needed):
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set

(Note: tried with CONFIG_SECURITY_CAPABILITIES=n and same result)

relevant line from strace starting bind:

# strace -ff named -u bind 2> /tmp/bind.log

...
capset(0x19980330, 0, {CAP_DAC_READ_SEARCH|CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE|CAP_SYS_CHROOT|CAP_SYS_RESOURCE, CAP _DAC_READ_SEARCH|CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE|CAP_SYS_CHROOT|CAP_SYS_RESOURCE, 0}) = -1 EPERM (Operation not
permitted)
...

What have I tried?

Tried it on two different systems, with the SEC CAP on and off.

Why do I think this is a kernel bug?

1) I revert to older kernel (2.6.22.1), no problems. Upgrade to 2.6.24.1. Problems.
2) Googling for "2.6.24 capset named" produces a lot of comments on the mm tree about a breakage. It looked like it was fixed, but I'm obviously not sure now.

So, someone please tell me either that I'm very very tired, and it must be my config, or that it IS a kernel bug, and hopefully provide a nice little patch to apply.

Once again, please CC me on replies,

Thanks,
Nick

#1 lore raw
Quoted 3 lines · Nick 'Zaf' Clifford

Please CC me on any/all replies

After trying to upgrade to deal with the most recent security issue, I

Judging by the 2.6.24.2 changelog I don't think the 2.6.24.1 kernel you grabbed has the fix you're looking for...

Quoted 30 lines

have encountered what has to either be me being very tired, or a kernel bug. After assuming that it was the former for 3 hours, I now conclude I'm more tired, and it has to be the latter.

Relevant versions:
Bind: 9.3.4
Kernel: Linux version 2.6.24.1.cerberus.1 (zaf@cerberus) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Mon Feb 11 20:05:58 NZDT 2008
Distro: Ubuntu Feisty
Processor: AMD Athlon

# cat /proc/cmdline
root=UUID=0996d997-a1f5-4601-964e-f3e71a477b81 ro quiet splash

Relevant .config settings (please let me know if more are needed):
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set

Quoted 1 line

(Note: tried with CONFIG_SECURITY_CAPABILITIES=n and same result)

Yeah my first thought was enough has been happening on the capabilities front that it could be an unfortunate patch merge, but 2.6.24.1 looks ok. So my next guess would be an selinux change. Though again i don't see anything obvious. Could you tell us what policy you use, and what context bind is starting in?

Quoted 12 lines

relevant line from strace starting bind:

# strace -ff named -u bind 2> /tmp/bind.log

...
capset(0x19980330, 0, {CAP_DAC_READ_SEARCH|CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE|CAP_SYS_CHROOT|CAP_SYS_RESOURCE, CAP _DAC_READ_SEARCH|CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE|CAP_SYS_CHROOT|CAP_SYS_RESOURCE, 0}) = -1 EPERM (Operation not
permitted)
...

Quoted 8 lines

What have I tried?

Tried it on two different systems, with the SEC CAP on and off.

Why do I think this is a kernel bug?

1) I revert to older kernel (2.6.22.1), no problems. Upgrade to 2.6.24.1. Problems.

Unfortunately that's quite a range...

Quoted 19 lines

2) Googling for "2.6.24 capset named" produces a lot of comments on the mm tree about a breakage. It looked like it was fixed, but I'm obviously not sure now.

So, someone please tell me either that I'm very very tired, and it must be my config, or that it IS a kernel bug, and hopefully provide a nice little patch to apply.

Once again, please CC me on replies,

Thanks,
Nick

--
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/

#2 lore raw

Re: if (2.6.24.1 && capset && bind9) bug() --RESOVLED

Quoted 10 lines · [email protected] wrote:
Quoted 4 lines · Nick 'Zaf' Clifford

Please CC me on any/all replies

After trying to upgrade to deal with the most recent security issue, I

Judging by the 2.6.24.2 changelog I don't think the 2.6.24.1 kernel you grabbed has the fix you're looking for...

Yes, that I realize now (I'll refer back to the lack of sleep thing caused by a long, long, long day), and speaking of which....... see below

Quoted 5 lines
Quoted 5 lines

have encountered what has to either be me being very tired, or a kernel bug. After assuming that it was the former for 3 hours, I now conclude I'm more tired, and it has to be the latter.

Quoted 7 lines

Yeah my first thought was enough has been happening on the capabilities front that it could be an unfortunate patch merge, but 2.6.24.1 looks ok. So my next guess would be an selinux change. Though again i don't see anything obvious. Could you tell us what policy you use, and what context bind is starting in?

2.6.24.2 seems to fix the issue, so thanks to whoever noticed and fixed that (and if no one fixed anything, then I'm just a raving loon, and you can move on with your day, content that the nice man raving about fictitious bugs is happy again).

But FYI and for what its worth, although SELinux was compiled, it isn't being used. Its disabled on boot.

Thanks for the reply and help anyways,

Nick