[EMAIL PROTECTED] wrote: > Quoting Nick 'Zaf' Clifford ([EMAIL PROTECTED]): > >> 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 >> 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. >> >> > 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 - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
