From: "Michael Schwarz" <mschwarz@multitool.net>
To: Ian Dall <ian@beware.dropbear.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Behavior of mdadm depending on user
Date: Tue, 3 Jul 2007 11:53:15 -0500 (CDT) [thread overview]
Message-ID: <2077.72.21.237.163.1183481595.squirrel@www.multitool.net> (raw)
In-Reply-To: <1183466429.395.44.camel@sibyl.beware.dropbear.id.au>
The problem with that approach is that it opens up the applications in
question to *any parameters* unlike the setuid C program which hardcodes the
parameters to the commands.
There is still a risk the binary may be modified, but it is lower than the
risk an attacker might be able to execute arbitrary "mdadm" and "mount/umount"
commands using sudo.
--
Michael Schwarz
> This isn't really an answer to your question, but isn't this an ideal
> application for sudo? Make a shell script with the mdadm command(s) you
> want. And set it up so apache or whatever your web server runs as able
> to run your shell script as root without authentication.
>
> Ian
> --
> Ian Dall <ian@beware.dropbear.id.au>
>
next prev parent reply other threads:[~2007-07-03 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 2:10 Behavior of mdadm depending on user Michael Schwarz
2007-07-03 12:40 ` Ian Dall
2007-07-03 16:53 ` Michael Schwarz [this message]
2007-07-03 17:28 ` Michael
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=2077.72.21.237.163.1183481595.squirrel@www.multitool.net \
--to=mschwarz@multitool.net \
--cc=ian@beware.dropbear.id.au \
--cc=linux-raid@vger.kernel.org \
/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