mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Mark Rosenstand <mark@borkware.net>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Executable shell scripts
Date: Sat, 13 May 2006 13:56:03 +0200	[thread overview]
Message-ID: <1147521363.3084.34.camel@gimli.at.home> (raw)
In-Reply-To: <20060513114509.3A90D146AF@hunin.borkware.net>

On Sat, 2006-05-13 at 13:45 +0200, Mark Rosenstand wrote:
> Bernd Petrovitsch <bernd@firmix.at> wrote:
> > On Sat, 2006-05-13 at 13:03 +0200, Mark Rosenstand wrote:
> > [...]
> > > A more useful case is when you setuid the script (and no, this doesn't
> > > need to be running as root and/or executable by all.)
> > 
> > Apart from the permission bug: This has been purposely disabled since it
> > is way to easy to write exploitable shell or other scripts.
> > Use a real programming languages, sudo or a trivial wrapper in C ....
s/languages/language/

And I forgot to mention that a kernel patch is another possibility.

> It isn't a bug on systems that support executable shell scripts.

I never wrote that (or anything which implies that directly).

> Doing security policy based on programming language seems weird at
> best, especially when the only user able to make those decisions is the
> superuser.

It boils down to "how easy is it for root to shoot in the foot"?
And the workarounds are somewhere between trivial and simple.

> Obviously the security-unaware people over at the OpenBSD camp must be
> completely clueless when they don't disallow the superuser to do this.

Of course this doesn't change the level of security but it plays with
the risk ....

> I'm looking forward to the day where I'm no longer allowed to make
> changes to /etc/ld.so.conf because it's a system file.
> 
> Anyway, is it possible to enable this functionality?

Yes.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


  reply	other threads:[~2006-05-13 12:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 10:38 Mark Rosenstand
2006-05-13 10:56 ` Arjan van de Ven
2006-05-13 11:03   ` Mark Rosenstand
2006-05-13 11:07     ` Arjan van de Ven
2006-05-13 11:17       ` Mark Rosenstand
2006-05-13 11:18       ` Willy Tarreau
2006-05-13 11:19       ` Douglas McNaught
2006-05-13 11:27         ` Mark Rosenstand
2006-05-13 11:37           ` Joel Jaeggli
2006-05-13 12:59           ` Theodore Tso
2006-05-13 13:18             ` Mark Rosenstand
2006-05-13 22:42               ` Neil Brown
2006-05-13 11:28         ` Stefan Smietanowski
2006-05-13 11:37           ` Neil Brown
2006-05-13 12:45             ` Willy Tarreau
2006-05-13 14:00         ` Arjan van de Ven
2006-05-13 20:52           ` Douglas McNaught
2006-05-13 11:16     ` J.A. Magallón
2006-05-13 11:22     ` Bernd Petrovitsch
2006-05-13 11:45       ` Mark Rosenstand
2006-05-13 11:56         ` Bernd Petrovitsch [this message]
2006-05-13 12:23           ` Mark Rosenstand
2006-05-13 12:58             ` Willy Tarreau
2006-05-13 18:55             ` Bernd Petrovitsch
2006-05-13 11:23     ` CaT
2006-05-13 11:00 ` Willy Tarreau

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=1147521363.3084.34.camel@gimli.at.home \
    --to=bernd@firmix.at \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@borkware.net \
    /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

all inboxes | Powered by JetHome®