All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Robert Evans <bob.evans@jhuapl.edu>
Subject: Re: Why doesn't chown produce an event
Date: Wed, 2 May 2007 13:30:59 -0400	[thread overview]
Message-ID: <200705021330.59459.sgrubb@redhat.com> (raw)
In-Reply-To: <4638AA93.7050108@jhuapl.edu>

On Wednesday 02 May 2007 11:13, Robert Evans wrote:
> If I log in as a typical user and try "chown bob /etc/shadow" I don't get
> an event produced, however if I try "chmod 666 /etc/shadow" I do.
>
> What am I missing here?

A syscall. If I am on a i386 machine and I strace chmod root file.txt, I see 
this:

chown32("file.txt", 0, -1)        = 0

So, you would want to use chown32 instead of chown on i386 machines. On x86_64 
the chown syscall is used.

-Steve

  parent reply	other threads:[~2007-05-02 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 15:13 Why doesn't chown produce an event Robert Evans
2007-05-02 15:14 ` Marcus Meissner
2007-05-02 15:45   ` Evans, Robert B.
2007-05-02 17:34     ` Steve Grubb
2007-05-02 17:30 ` Steve Grubb [this message]
2007-05-02 18:00   ` Robert Evans
2007-05-02 18:15     ` Steve Grubb

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=200705021330.59459.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=bob.evans@jhuapl.edu \
    --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.