From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: SOFTWARE_UPDATE on RHEL 7.6
Date: Wed, 29 Aug 2018 14:34:39 -0400 [thread overview]
Message-ID: <1601219.lEonBTiIkC@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F790010BAE1F13A8@FRVDX103.fr01.awl.atosorigin.net>
Hello,
On Wednesday, August 29, 2018 9:53:05 AM EDT Maupertuis Philippe wrote:
> I have tried to get the SOFTWARE_UPDATE events on a new RHEL 7.6 beta 1
> with audit rebased on 2.8.4 When installing a new rpm I get the
> corresponding event.
> The text format is very easily readable :)
> Unfortunately when I remove the package I get nothing.
> Is it the intending behavior ?
Yes. That is the intended behavior. If package removal events are desired, a
bug report may be filed. OSPP v4.2 requirements are concerned about software
being installed and upgraded. It is silent on software removal.
> If updates are pushed through Redhat satellite or Spacewalk would I get
> the event ?
The patch is in librpm, so it should be recorded by anything that uses it.
-Steve
prev parent reply other threads:[~2018-08-29 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 13:53 SOFTWARE_UPDATE on RHEL 7.6 Maupertuis Philippe
2018-08-29 18:34 ` Steve Grubb [this message]
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=1601219.lEonBTiIkC@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=philippe.maupertuis@equensworldline.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