Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Cc: Roger Moore <embedded_systems@hotmail.co.uk>
Subject: Re: Removing Audit-libs, Python3-audit
Date: Wed, 23 Feb 2022 14:35:03 -0500	[thread overview]
Message-ID: <8064746.lOV4Wx5bFT@x2> (raw)
In-Reply-To: <AM0PR07MB558763A52EE429F3B5073E91B53C9@AM0PR07MB5587.eurprd07.prod.outlook.com>

Hello,

On Wednesday, February 23, 2022 1:32:31 PM EST Roger Moore wrote:
>      Can you let me know how to remove all audit code, including audit-libs
> and python3-audit, and stop them from being updated by DNF update.
> 
> DNF keeps reinstalling the python3 code (audit-libs python3-audit).
> 
> I have  exclude=audit-libs,python3-audit in /etc/yum.conf
> 
> But, it keeps on reinstalling.

rpmreaper is a good tool to check dependencies. On my system is shows these 
packages pull it in:

        5.4M ┌─< python3-policycoreutils   3.3-1.fc35.noarch
  o     1.3M ├─< setroubleshoot-server     3.3.28-3.fc35.x86_64
        336K python3-audit             3.0.8-1.fc35.x86_64                      

audit-libs is likely impossible to remove. Pam and shadow-utils link against 
it. Unfortunately, systemd turns auditing on. But if you boot with the kernel 
audit=0 option and disable the systemd-journald-audit.socket, you should not 
get any audit events.

Hope this helps...

-Steve



--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2022-02-23 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 18:32 Removing Audit-libs, Python3-audit Roger Moore
2022-02-23 19:35 ` Steve Grubb [this message]
2022-02-23 20:19 ` Enzo Matsumiya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8064746.lOV4Wx5bFT@x2 \
    --to=sgrubb@redhat.com \
    --cc=embedded_systems@hotmail.co.uk \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox