public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "MAUPERTUIS, PHILIPPE" <philippe.maupertuis@equensworldline.com>
Subject: Re: RHEL 8  audit rules
Date: Wed, 06 Nov 2019 11:49:56 -0500	[thread overview]
Message-ID: <11239651.W6AYHMhLza@x2> (raw)
In-Reply-To: <5F4EE10832231F4F921A255C1D95429819F47E@DEERLM99EX7MSX.ww931.my-it-solutions.net>

On Wednesday, November 6, 2019 4:39:54 AM EST MAUPERTUIS, PHILIPPE wrote:
> The rules proposed in /usr/share/doc/audit/rules/ contain 32 bits stuff.
> For example :
> ## 10.2.5.b All elevation of privileges is logged
> -a always,exit -F arch=b64 -S setuid -F a0=0 -F exe=/usr/bin/su -F
> key=10.2.5.b-elevated-privs-session -a always,exit -F arch=b32 -S setuid
> -F a0=0 -F exe=/usr/bin/su -F key=10.2.5.b-elevated-privs-session
> 
> Is it still necessary for RHEL 8 ?

For RHEL8 itself, no. But the 32 bit ABI is available for legacy programs.

> Would the 21-no32bit.rules be enough ?

If you know for certain that no 32 bit apps will ever be used, then yes. And 
then you can also delete all 32 bit rules to improve performance.

This gives me an idea that perhaps the sample rules could be split up into 32 
and 64 bit so that we can improve system performance ever so slightly.

> Can we run any 32 bits binary on rhel 8 ?

Yep. And that also means that a malicious python program can call the 32bit 
ABI in an attempt at avoiding detection.

-Steve

      reply	other threads:[~2019-11-06 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  9:39 RHEL 8 audit rules MAUPERTUIS, PHILIPPE
2019-11-06 16:49 ` 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=11239651.W6AYHMhLza@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