linux-kernel - Re: [PATCH ghak111 V1] audit: deliver siginfo regarless of syscall

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190411142247.1a7a3639@ivy-bridge>
Date:   Thu, 11 Apr 2019 14:22:47 +0200
From:   Steve Grubb <sgrubb@...hat.com>
To:     Richard Guy Briggs <rgb@...hat.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux-Audit Mailing List <linux-audit@...hat.com>,
        Paul Moore <paul@...l-moore.com>, omosnace@...hat.com,
        eparis@...isplace.org, ebiederm@...ssion.com, oleg@...hat.com
Subject: Re: [PATCH ghak111 V1] audit: deliver siginfo regarless of syscall

On Tue, 9 Apr 2019 11:57:28 -0400
Richard Guy Briggs <rgb@...hat.com> wrote:

> On 2019-04-09 17:37, Steve Grubb wrote:
> > On Tue, 9 Apr 2019 10:02:59 -0400
> > Richard Guy Briggs <rgb@...hat.com> wrote:
> >   
> > > On 2019-04-09 08:01, Steve Grubb wrote:  
> > > > On Mon,  8 Apr 2019 23:52:29 -0400 Richard Guy Briggs
> > > > <rgb@...hat.com> 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.  
> 
> If auditing is disabled in the kernel, none of this is trackable.  It
> is for those as yet unsupported arches that can run audit enabled but
> without auditsyscall support.

Ok. I suppose this is useful for this use case. No further objections.

-Steve