Linux-audit Archive on lore.kernel.org
 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: passwd and USER_CHAUTHTOK
Date: Wed, 30 Aug 2017 15:02:53 -0400	[thread overview]
Message-ID: <1710054.zz21I9x0fd@x2> (raw)
In-Reply-To: <1814694.A4XjMbMWtj@x2>

On Wednesday, August 30, 2017 10:22:43 AM EDT Steve Grubb wrote:
> Hello Philippe,
> 
> Thanks for reporting this (and the other bug which is in my queue to work
> on).
> On Wednesday, August 30, 2017 3:56:10 AM EDT Maupertuis Philippe wrote:
> > Hi
> > On a new redhat 7.4, passwd -S to check the status of a user generates the
> > following event  : node=xxxxx type=USER_CHAUTHTOK msg=audit(28/08/17
> > 16:34:18.632:54145) : pid=31134 uid=root auid=xxxxx ses=3866
> > msg='op=password status displayed for user id=ftp exe=/usr/bin/passwd
> > hostname= xxxxx addr=? terminal=pts/1 res=success'
> > 
> > According to
> > https://github.com/linux-audit/audit-documentation/wiki/SPEC-User-Account-
> > L
> > ifecycle-Events  USER_CHAUTHTOK means that the user  has successfully
> > changed his password. In that case no change were done, only a query as it
> > appears in the msg field
> > 
> > The text format is even more disturbing :
> > On xxxxx at 16:34:18 28/08/17 xxxxx, acting as root, successfully
> > changed-password using /usr/bin/passwd The real action and the target user
> > (ftp) is entirely lost in the text format.
> > 
> > I would say that this message should not have been generated in the first
> > place.
> 
> I would agree. I'll make a patch to remove it.

In case anyone wants this update to passwd, it is here:

https://pagure.io/passwd/c/c461efa0b6f9134adbb1440bb8cef2d3bf81620d?branch=master


> I looked around the auditing in passwd and it looks like it has not been
> updated as everything else has been to eliminate dangling text. So, it's
> wholly unsuited as is for text format output. I'll make a second patch to
> update the auditing to modern standards. Its probably not been touched in a
> decade.

And the other audit cleanups here:

https://pagure.io/passwd/c/d02e152112b28717eece1d64027a325439968e9f?branch=master

https://pagure.io/passwd/c/137db0d6f2fd668081133c172ae7726d28ce95b6?branch=master

-Steve

      reply	other threads:[~2017-08-30 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  7:56 passwd and USER_CHAUTHTOK Maupertuis Philippe
2017-08-30 14:22 ` Steve Grubb
2017-08-30 19:02   ` 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=1710054.zz21I9x0fd@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