From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH ghak111 V1] audit: deliver siginfo regarless of syscall Date: Tue, 9 Apr 2019 17:37:16 +0200 Message-ID: <20190409173716.1a0308fb@ivy-bridge> References: <20190409080138.745d18a1@ivy-bridge> <20190409140259.n4t6rxb24eu3uzvp@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190409140259.n4t6rxb24eu3uzvp@madcap2.tricolour.ca> Sender: linux-kernel-owner@vger.kernel.org To: Richard Guy Briggs Cc: LKML , Linux-Audit Mailing List , Paul Moore , omosnace@redhat.com, eparis@parisplace.org, ebiederm@xmission.com, oleg@redhat.com List-Id: linux-audit@redhat.com On Tue, 9 Apr 2019 10:02:59 -0400 Richard Guy Briggs wrote: > On 2019-04-09 08:01, Steve Grubb wrote: > > On Mon, 8 Apr 2019 23:52:29 -0400 Richard Guy Briggs > > wrote: > > > When a process signals the audit daemon (shutdown, rotate, resume, > > > reconfig) but syscall auditing is not enabled, we still want to > > > know the identity of the process sending the signal to the audit > > > daemon. > > > > Why? If syscall auditing is disabled, then there is no requirement > > to provide anything. What is the real problem that you are seeing? > > Shutdown messages with -1 in them rather than the real values. OK. We can fix that by patching auditd to see if auditing is enabled before requesting signal info. If auditing is disabled, the proper action is for the kernel to ignore any audit userspace messages except the configuration commands. -Steve