From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.3 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25016C433DB for ; Thu, 11 Mar 2021 10:31:40 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 69BB864FC0 for ; Thu, 11 Mar 2021 10:31:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 69BB864FC0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=linux-audit-bounces@redhat.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-389-EK8HUSkTNKioUhShGLKOkg-1; Thu, 11 Mar 2021 05:31:33 -0500 X-MC-Unique: EK8HUSkTNKioUhShGLKOkg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8A531801596; Thu, 11 Mar 2021 10:31:29 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9CE581A879; Thu, 11 Mar 2021 10:31:28 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id CAF9918155DE; Thu, 11 Mar 2021 10:31:26 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 12BAVPBS018011 for ; Thu, 11 Mar 2021 05:31:25 -0500 Received: by smtp.corp.redhat.com (Postfix) id 151692166B44; Thu, 11 Mar 2021 10:31:25 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast01.extmail.prod.ext.rdu2.redhat.com [10.11.55.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0E6A62156A21 for ; Thu, 11 Mar 2021 10:31:22 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C4578857CFD for ; Thu, 11 Mar 2021 10:31:22 +0000 (UTC) Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-550-HoQV7dVsNQCugBemH4XltA-1; Thu, 11 Mar 2021 05:31:19 -0500 X-MC-Unique: HoQV7dVsNQCugBemH4XltA-1 Received: by mail-ej1-f49.google.com with SMTP id p7so33775432eju.6; Thu, 11 Mar 2021 02:31:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wsPQV+WImwrB+VD0MWE2xHmueHPLw39sh/hlfOENrnQ=; b=ILUfNWC3b1zCLOHSXVKC1rePfPqjiP1TPLiD/YGMP/dD4ewL7YhS8YsM0iI6I+rivI pznNmCL2mRp0Y/U1lC7vebNsxPnz7D1xUVvFjPx6T/axPLUw2jC5uodeEErptO4OYwAL Tq9aTql9Ul+KlrVsrKEL06cxqjhws5SYojl9X8EUCfuRlHONTmklxTNHzKEyrpZeybTf XkqzuoSuuNLQ3oYDHLOkVcYPQpixnDTV7B9CzHpWZYnvQbvLPc8wcQfROuodOiCXgrFu qRDJ4e7XoKOORDnPgv3ocsqfPf4XAoAcYHRZC+UbLHzFx1K5ISlEDVUt96sg8cwCSadf S23A== X-Gm-Message-State: AOAM531dUd6R3QP7lhsE1Ifjp+EbYFrpHdApBE+yjbg+C7XU8f423vPJ YAH1AWwCi+iROjnUUKQtUh34KRKBB6k5iKzLEdgI9p9CaPthFg== X-Google-Smtp-Source: ABdhPJzJQkiqjwumhbRoEgHURfPK5jjg7ZJj4R0qOcbPtLKMCxGCmRYws/UUAuBZR903zwUyI0441OheuoNFlj8eyXI= X-Received: by 2002:a17:906:7f84:: with SMTP id f4mr2293745ejr.525.1615458677741; Thu, 11 Mar 2021 02:31:17 -0800 (PST) MIME-Version: 1.0 References: <3428581.R56niFO833@x2> In-Reply-To: <3428581.R56niFO833@x2> From: Alan Evangelista Date: Thu, 11 Mar 2021 07:31:06 -0300 Message-ID: Subject: Re: renameat2 syscall is not recorded To: Steve Grubb X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-loop: linux-audit@redhat.com Cc: Linux-Audit Mailing List X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=linux-audit-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/mixed; boundary="===============7901779966918755049==" --===============7901779966918755049== Content-Type: multipart/alternative; boundary="000000000000a2db3405bd404805" --000000000000a2db3405bd404805 Content-Type: text/plain; charset="UTF-8" AE> Is there any reason why (...) auditctl -R don't print errors to stdout when rules parsing errors occur? SG> If it's detected that the rules are in a file, they get sent to syslog because > 99.99% of the time, this is system boot or initscripts and we need to make > the problem discoverable later by the system admin. I assume you meant "if it's detected that there are errors in the rules in a rules file". IMHO the stream to which errors are output (syslog or stdout) should be configurable, as it is *very* confusing to run auditctl -R manually and get no errors when there is an error in rules parsing. It forces the user to always run "auditctl -R" and "auditctl -l" to check if the rules are indeed active, which is not intuitive at all. Regarding the initscript use case, I think it's also very common to use "auditctl -R" while creating new audit rules. On Wed, Mar 10, 2021 at 4:06 PM Steve Grubb wrote: > On Wednesday, March 10, 2021 5:53:42 AM EST Alan Evangelista wrote: > > OM> Not sure if this is it, but there is a "-" missing before the "S" > > before "renameat2". > > > > This was indeed the issue. I found our that was the issue when I ran > > "auditctl -l". Thank you. > > > > Is there any reason why augenrules > > It has no idea about the rules, it simply compiles the master list. > > > and auditctl -R don't print errors to stdout when rules parsing errors > > occur? > > If it's detected that the rules are in a file, they get sent to syslog > because > 99.99% of the time, this is system boot or initscripts and we need to make > the problem discoverable later by the system admin. > > -Steve > > > --000000000000a2db3405bd404805 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
AE&g= t;=C2=A0=C2=A0Is there any reason why (...)=C2=A0auditctl -R don't prin= t errors to stdout when rules parsing errors occur?

SG> If= it's detected that the rules are in a file, they get sent to syslog be= cause
=C2=A0 =C2=A0 =C2=A0>=C2=A099.99% of the time, this is system = boot or initscripts and we need to make
=C2=A0 =C2=A0 =C2=A0>= =C2=A0the problem discoverable later by the system admin.
I assume you meant "if it's detected that there are er= rors in the rules in a rules file".
IMHO the stream to which= errors are output (syslog or stdout) should be configurable,
as = it is *very* confusing to run auditctl -R manually and get no errors when t= here is an
error in rules parsing. It forces the user to always r= un "auditctl -R" and "auditctl -l" to check
i= f the rules are indeed active, which is not intuitive at all. Regarding the= initscript use case,
I think it's also very common to use &q= uot;auditctl -R" while creating new audit rules.

On Wed, Mar 10, = 2021 at 4:06 PM Steve Grubb <sgrubb= @redhat.com> wrote:
On Wednesday, March 10, 2021 5:53:42 AM EST Alan Evangelista wro= te:
> OM> Not sure if this is it, but there is a "-" missing be= fore the "S"
> before "renameat2".
>
> This was indeed the issue. I found our that was the issue when I ran > "auditctl -l". Thank you.
>
> Is there any reason why augenrules

It has no idea about the rules, it simply compiles the master list.

> and auditctl -R don't print errors to stdout when rules parsing er= rors
> occur?

If it's detected that the rules are in a file, they get sent to syslog = because
99.99% of the time, this is system boot or initscripts and we need to make =
the problem discoverable later by the system admin.

-Steve


--000000000000a2db3405bd404805-- --===============7901779966918755049== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit --===============7901779966918755049==--