From: Steve Grubb <sgrubb@redhat.com>
To: Dean Anderson <dean@av8.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: Decoder for log messages???
Date: Mon, 5 Nov 2007 18:23:16 -0500 [thread overview]
Message-ID: <200711051823.17175.sgrubb@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0711051620330.20094-100000@citation2.av8.net>
On Monday 05 November 2007 04:28:29 pm Dean Anderson wrote:
> > and such a pathname will always be process-local and not guaranteed to
> > be meaningful, stable, or the actual path by which the file was
> > accessed.
>
> ?? The filesystem is not process local, except perhaps /proc
I think what he means is that if you have symlinks somewhere in the path or
bind mount overlays, there could be several ways of identifying the same
file. This is partly why the inode and filesystem is given. It helps identify
exactly what is being accessed.
-Steve
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-11-05 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 4:17 Decoder for log messages??? Dean Anderson
2007-10-31 14:26 ` Stephen Smalley
2007-10-31 22:44 ` Russell Coker
2007-11-05 21:28 ` Dean Anderson
2007-11-05 23:15 ` Steve Grubb
2007-11-05 23:23 ` Steve Grubb [this message]
2007-11-06 14:07 ` Stephen Smalley
2010-12-01 0:17 ` What can selinux do that "audit" by itself cant do ? Hasan Rezaul-CHR010
2010-12-01 13:44 ` Steve Grubb
2010-12-01 18:06 ` Hasan Rezaul-CHR010
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=200711051823.17175.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=dean@av8.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.