On 2012-10-04 23:30 +0200, Stefan Richter wrote: > On Oct 04 Nick Bowler wrote: > > On 2012-10-04 09:14 -0700, Kees Cook wrote: > > > On Thu, Oct 04, 2012 at 12:03:54PM -0400, Nick Bowler wrote: > > > > On 2012-10-04 08:49 -0700, Kees Cook wrote: > > > > > FWIW, there should have been an audit message about it in dmesg. [...] > > > > # dmesg > > > > (no output) > > > > > > Well that's sad. :( Two situations I can think of for that: > > > - the kernel wasn't build with CONFIG_AUDIT > > > > Indeed, I do not have this option enabled. Why would I have it? The > > description says it's for SELinux, which I do not use. > > It says it is /among else/ for SELinux. Another user appears to be > ConsoleKit, which wants CONFIG_AUDITSYSCALL, which depends on CONFIG_AUDIT.
Indeed, you are correct that the help text does imply that there are (potentially) other users besides SElinux, although it does not say what they are. Regardless, the point is that I have no idea why I would have this optional feature enabled, as I still don't even know what it does because the help text doesn't actually say. I even found a website, http://people.redhat.com/sgrubb/audit/, which seems to be related to this feature but even here I cannot find one sentence explaining what the feature is. Well, from this thread I now know that this feature enables, at least in some cases, printk messages when your previously-working scripts are broken by a kernel update. Cheers, -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
