From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Bigonville Subject: Bug#759604: Any problem with making auditd log readable by the adm group? Date: Wed, 11 May 2016 09:55:33 +0200 Message-ID: References: <85futrf3ts.fsf@boum.org> Reply-To: Laurent Bigonville , 759604@bugs.debian.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Resent-To: debian-bugs-dist@lists.debian.org Resent-Message-ID: In-Reply-To: <85futrf3ts.fsf@boum.org> List-URL: List-Post: List-Help: List-Subscribe: List-Unsubscribe: To: intrigeri , 759604@bugs.debian.org, linux-audit@redhat.com List-Id: linux-audit@redhat.com Le 09/05/16 =E0 21:07, intrigeri a =E9crit : > Hi, Hey, > in Debian, the convention for many log files is to make them readable > by members of the adm group. We're considering doing the same for the > auditd logs, in order to make apparmor-notify work out-of-the-box. Shouldn't apparmor-notify use the audispd to get the events instead of=20 parsing directly the logs? I'm not objecting changing the permissions in debian, but I'm wondering=20 if it shouldn't be better to do it like that, I think that the=20 setroubleshoot (a SELinux troubleshooting service used in RHEL/Fedora)=20 is doing it like that. Cheers, Laurent Bigonville