mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Paul Moore <pmoore@redhat.com>,
	linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	eparis@redhat.com, v.rathor@gmail.com, ctcard@hotmail.com
Subject: Re: [PATCH V3 1/2] audit: stop an old auditd being starved out by a new auditd
Date: Tue, 22 Dec 2015 10:46:08 -0500	[thread overview]
Message-ID: <20151222154608.GG29776@madcap2.tricolour.ca> (raw)
In-Reply-To: <2432137.V5S5oOaA09@x2>

On 15/12/22, Steve Grubb wrote:
> On Tuesday, December 22, 2015 09:24:56 AM Paul Moore wrote:
> > On Tuesday, December 22, 2015 04:03:06 AM Richard Guy Briggs wrote:
> > > Nothing prevents a new auditd starting up and replacing a valid
> > > audit_pid when an old auditd is still running, effectively starving out
> > > the old auditd since audit_pid no longer points to the old valid auditd.
> > > 
> > > If no message to auditd has been attempted since auditd died unnaturally
> > > or got killed, audit_pid will still indicate it is alive.  There isn't
> > > an easy way to detect if an old auditd is still running on the existing
> > > audit_pid other than attempting to send a message to see if it fails.
> > > An -ECONNREFUSED almost certainly means it disappeared and can be
> > > replaced.  Other errors are not so straightforward and may indicate
> > > transient problems that will resolve themselves and the old auditd will
> > > recover.  Yet others will likely need manual intervention for which a
> > > new auditd will not solve the problem.
> > > 
> > > Send a new message type (AUDIT_REPLACE) to the old auditd containing a
> > > u32 with the PID of the new auditd.  If the audit replace message
> > > succeeds (or doesn't fail with certainty), fail to register the new
> > > auditd and return an error (-EEXIST).
> > > 
> > > This is expected to make the patch preventing an old auditd orphaning a
> > > new auditd redundant.
> > > 
> > > V3: Switch audit message type from 1000 to 1300 block.
> > > 
> > > Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
> > > ---
> > > 
> > >  include/uapi/linux/audit.h |    1 +
> > >  kernel/audit.c             |   16 +++++++++++++++-
> > >  2 files changed, 16 insertions(+), 1 deletions(-)
> > > 
> > > diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/audit.h
> > > index 843540c..d820aa9 100644
> > > --- a/include/uapi/linux/audit.h
> > > +++ b/include/uapi/linux/audit.h
> > > @@ -110,6 +110,7 @@
> > > 
> > >  #define AUDIT_SECCOMP		1326	/* Secure Computing event */
> > >  #define AUDIT_PROCTITLE		1327	/* Proctitle emit event */
> > >  #define AUDIT_FEATURE_CHANGE	1328	/* audit log listing feature changes
> > 
> > */
> > 
> > > +#define AUDIT_REPLACE		1329	/* Replace auditd if this packet...
> > 
> > Steve, are you okay with this record number?
> 
> Yes. Just wondering what to do with the event.

There's a u32 in it with the pid of the process trying to hijack/replace
the one the kernel thinks still exists, so it is worth recording that
information, I think, if the old auditd actually receives this message.

> -Steve

- RGB

--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545

  reply	other threads:[~2015-12-22 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  9:03 Richard Guy Briggs
2015-12-22  9:03 ` [PATCH V3 2/2] audit: log failed attempts to change audit_pid configuration Richard Guy Briggs
2015-12-22 23:47   ` Paul Moore
2015-12-22 14:24 ` [PATCH V3 1/2] audit: stop an old auditd being starved out by a new auditd Paul Moore
2015-12-22 14:56   ` Steve Grubb
2015-12-22 15:46     ` Richard Guy Briggs [this message]
2015-12-22 23:47 ` Paul Moore

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=20151222154608.GG29776@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=ctcard@hotmail.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmoore@redhat.com \
    --cc=sgrubb@redhat.com \
    --cc=v.rathor@gmail.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

all inboxes | Powered by JetHome®