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
| ||
|
Date: Tue, 7 Mar 2017 10:41:39 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Richard Guy Briggs <rgb@...hat.com> Cc: Paul Moore <paul@...l-moore.com>, Linux-Audit Mailing List <linux-audit@...hat.com>, LKML <linux-kernel@...r.kernel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Ingo Molnar <mingo@...hat.com>, Al Viro <viro@...iv.linux.org.uk> Subject: Re: Hundreds of null PATH records for *init_module syscall audit logs On Mon, 6 Mar 2017 22:39:54 -0500 Richard Guy Briggs <rgb@...hat.com> wrote: > >From the output I've seen, it doesn't look particularly useful, but it > was useful to finally see the source of those huge numbers of PATH > records. Here's an fpaste: > https://paste.fedoraproject.org/paste/UpZoYuokojR0es1ayNdx5l5M1UNdIGYhyRLivL9gydE=/ Those are the files for the module's trace events that are created. I'm still confused about what the issue is. -- Steve
Powered by blists - more mailing lists