From: David Smith <dsmith@redhat.com>
To: Pavel Kankovsky <peak@argo.troja.mff.cuni.cz>
Cc: grundy <grundym@us.ibm.com>,
fedora-security-list@redhat.com,
Systemtap List <systemtap@sources.redhat.com>
Subject: Re: Need some security advice for systemtap
Date: Mon, 11 Jun 2007 13:09:00 -0000 [thread overview]
Message-ID: <466D4979.7010306@redhat.com> (raw)
In-Reply-To: <20070608211641.13DE.0@paddy.troja.mff.cuni.cz>
Thanks for the response. See stuff below.
Pavel Kankovsky wrote:
> On Mon, 4 Jun 2007, David Smith wrote:
>
>> One of the complaints we get from users is that we require root access
>> (using sudo) to install/remove the kernel module. Large enterprise
>> customers typically don't give out sudo access to all admins. So, they
>> would like a way to designate certain scripts/modules as "blessed", and
>> allow admins/developers/etc. without root access to run those "blessed"
>> scripts/modules.
>
> The easiest way to designate a certain script as "blessed" (and quite
> difficult to goof it up) is to let a trusted user take the source of the
> script, check it, make a kernel module, and install it into a designated
> directory on the target system (or systems), perhaps under
> "/lib/modules/$version".
That's my current thinking. Seems easier from a user's point of view
and less fragile from a security point of view.
> If you are afraid of allowing "untrusted admins" run "sudo modprobe
> the_probe" (but not afraid of allowing to run your own setuid root
> program) you can create something like "sustaprun" that will make it
> possible to load blessed modules (from the designated directory) only.
That's also my current thinking. I'm trying to prototype this now.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2007-06-11 13:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 19:34 David Smith
2007-06-05 8:47 ` Tomasz Chmielewski
2007-06-05 15:09 ` Frank Ch. Eigler
2007-06-05 20:40 ` David Smith
2007-06-05 17:20 ` grundy
2007-06-05 20:56 ` David Smith
2007-06-08 22:00 ` Pavel Kankovsky
2007-06-11 13:09 ` David Smith [this message]
2007-06-11 18:35 ` David Smith
2007-06-11 21:32 ` Frank Ch. Eigler
2007-06-11 22:00 ` David Smith
2007-06-16 15:35 ` Pavel Kankovsky
2007-06-18 19:45 ` David Smith
2007-06-19 0:02 ` Martin Hunt
2007-06-19 19:57 ` David Smith
2007-06-19 20:42 ` Stone, Joshua I
2007-07-01 16:14 ` Pavel Kankovsky
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=466D4979.7010306@redhat.com \
--to=dsmith@redhat.com \
--cc=fedora-security-list@redhat.com \
--cc=grundym@us.ibm.com \
--cc=peak@argo.troja.mff.cuni.cz \
--cc=systemtap@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).