All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Cc: Ivan Castell <icastell@circontrol.com>
Subject: Re: auditd daemon is changing /tmp permissions
Date: Thu, 04 Mar 2021 11:05:34 -0500	[thread overview]
Message-ID: <2572156.mvXUDI8C0e@x2> (raw)
In-Reply-To: <AM6PR05MB59286D712733FF9CFA4BAED8A3979@AM6PR05MB5928.eurprd05.prod.outlook.com>

Hello,

On Thursday, March 4, 2021 10:45:03 AM EST Ivan Castell wrote:
> Just testing different versions of audit, discovered that version 2.8.5 and
> 3.0.1 are changing permissions of /tmp from 1777 to 700. This is a problem
> as normal non-root users can't write in /tmp after starting autitd.
> 
> The problem is related with the daemon, as commenting this call:
> 
> start-stop-daemon -S -q -p ${PIDFILE} --exec ${DAEMON}
> 
> fixes the issue.
> 
> It works fine on version 2.8.2.
> 
> We fixed temporaly setting proper /tmp permissions after starting the
> daemon:
> 
> # Run audit daemon executable
> start-stop-daemon -S -q -p ${PIDFILE} --exec ${DAEMON}
> 
> if [ $? = 0 ]; then
> # Load the default rules
> test -f /etc/audit/rules.d/audit.rules && /usr/sbin/auditctl -R
> /etc/audit/rules.d/audit.rules >/dev/null # Bugfix audit 2.8.5 (reported
> and waiting for a patch!)
> chmod 1777 /tmp
> echo "OK"
> else
> echo "FAIL"
> fi
> 
> Could you provide a temporal patch for the daemon?

Hmm...

[audit-3.0.2]$ grep -rl start-stop-daemon *
[audit-3.0.2]$ grep -rl 'test -f /etc/audit/rules.d/audit.rules' *
[audit-3.0.2]$ 

I don't see this in the audit source code. Which file is this in?

-Steve



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


      reply	other threads:[~2021-03-04 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 15:45 auditd daemon is changing /tmp permissions Ivan Castell
2021-03-04 16:05 ` 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=2572156.mvXUDI8C0e@x2 \
    --to=sgrubb@redhat.com \
    --cc=icastell@circontrol.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.