From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: Joshua Brindle <method@manicmethod.com>,
Joshua Brindle <method@gentoo.org>,
russell@coker.com.au, selinux@tycho.nsa.gov,
Stephan Mueller <smueller@atsec.com>
Subject: Re: type transitioning script race condition?
Date: Thu, 31 Aug 2006 16:02:33 -0400 [thread overview]
Message-ID: <1157054553.26051.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20060831171908.GF12307@w-m-p.com>
On Thu, 2006-08-31 at 12:19 -0500, Klaus Weidner wrote:
> On Thu, Aug 31, 2006 at 12:39:10PM -0400, Karl MacMillan wrote:
> > On Thu, 2006-08-31 at 11:02 -0500, Klaus Weidner wrote:
> > > - create link to executable (the link can be one of the path components),
> > > for example:
> > >
> > > ln -s /usr/sbin /tmp/hack
> >
> > In a strict environment the creation of the symlinks to privileged
> > applications should be controlled.
>
> Yes, but this gets tricky in a case like this where the symlink just
> points to a directory used as a path component, and stat()ing the
> executable file won't reveal that it's accessed through a link. You'd
> need to very restrictive about symlinks, for example not permitting links
> pointing to something you don't own or can't write.
>
And perhaps the bigger issue is that I am totally making up the ability
to control what target a symlink has (as was pointed out by Dave Caplan
in a private mail). The only control we get is the creation of symlinks
not control over their targets.
Karl
--
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:[~2006-08-31 20:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:39 type transitioning script race condition? Klaus Weidner
2006-08-30 23:18 ` Russell Coker
2006-08-31 3:12 ` Joshua Brindle
2006-08-31 13:23 ` Karl MacMillan
2006-08-31 13:53 ` Joshua Brindle
2006-08-31 15:29 ` Karl MacMillan
2006-08-31 15:41 ` Joshua Brindle
2006-08-31 16:02 ` Klaus Weidner
2006-08-31 16:39 ` Karl MacMillan
2006-08-31 17:19 ` Klaus Weidner
2006-08-31 20:02 ` Karl MacMillan [this message]
2006-08-31 15:46 ` Klaus Weidner
2006-08-31 16:13 ` Joshua Brindle
2006-08-31 16:40 ` Klaus Weidner
2006-09-01 11:37 ` Stephen Smalley
2006-09-01 12:48 ` Russell Coker
2006-09-01 13:13 ` Joshua Brindle
2006-08-31 14:43 ` Stephen Smalley
2006-08-31 14:49 ` Joshua Brindle
2006-08-31 15:09 ` Stephen Smalley
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=1157054553.26051.5.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=klaus@atsec.com \
--cc=method@gentoo.org \
--cc=method@manicmethod.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--cc=smueller@atsec.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.