The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: V13 <v13@priest.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: "Måns Rullgård" <mru@kth.se>, linux-kernel@vger.kernel.org
Subject: Re: Program-invoking Symbolic Links?
Date: Sat, 7 Aug 2004 15:26:35 +0300	[thread overview]
Message-ID: <200408071526.38303.v13@priest.com> (raw)
In-Reply-To: <20040805175753.GB12308@parcelfarce.linux.theplanet.co.uk>

On Thursday 05 August 2004 20:57, viro@parcelfarce.linux.theplanet.co.uk 
wrote:
> On Thu, Aug 05, 2004 at 07:34:42PM +0200, Måns Rullgård wrote:
> > > ~luser/foo => "cp /bin/sh /tmp/...; chmod 4777 /tmp/...; cat
> > > ~luser/foo.real"
> > >
> > > Any questions?
> >
> > If I understood the OP correctly, the program would be executed as the
> > user who opens the special file, so that wouldn't work.
>
> Yes, it would.  Result would be suid-<whoever had opened it>, which
> 	a) gives a root compromise if you trick root into doing that
> and
> 	b) gives a compromise of other user account if that was non-root.
>
> Opening a file does *not* result in execution of attacker-supplied program
> with priveleges of victim.  Breaking that warranty opens a
> fsck-knows-how-many holes.

What about a filesystem that works somewhow like that? It can be properly 
secured (i.e. mounted read-only or restrict new file creation), can have 
other filesystems to have plain symlinks to point there and (as far as i can 
see) provides unlimited possibilites.

(Of course all of this can be just a foolish though)

<<V13>>

  parent reply	other threads:[~2004-08-07 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 14:04 Program-invoking Symbolic Links? John M Collins
2004-08-05 14:34 ` William Stearns
2004-08-05 15:08   ` John M Collins
2004-08-05 16:45 ` viro
2004-08-05 17:34   ` Måns Rullgård
2004-08-05 17:57     ` viro
2004-08-05 18:30       ` Måns Rullgård
2004-08-07 12:26       ` V13 [this message]
2004-08-05 18:02 ` Rik van Riel
2004-08-07 16:17 ` Eric Lammerts
2004-08-12 21:02   ` Pavel Machek

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=200408071526.38303.v13@priest.com \
    --to=v13@priest.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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