Re: multicast listeners and audit events to kmsg

> In systemd we just think that audit information is pretty interesting > even if you don't want to buy into the whole government regulation > stuff, even if you don't want the auditd to run, and the full audit > package installed. i.e. we want to collect the data as one of our > various data streams, as a secondary consumer of it, and leave it to > the audit package itself to do everything else and be the primary > consumer of it. > > Using the multicast group is our way of saying: "we don't want to own > the audit stream, you can keep it; we just want to have a look > too". The problem is that on systems without a running audit daemon there is no one to "own" the audit stream so it floods the kmsg, spills onto the console, and everyone's feet get wet. Are we going to blame the source of the stream, or the person who turned on the tap in the first place and caused the mess?

If systemd enables the audit stream, and doesn't want the stream to flood kmsg, it needs to make sure that the stream is directed to a suitable sink, be it auditd or some other daemon.