From: "Peter Teoh" <htmldeveloper@gmail.com>
To: "Geoffrey McRae" <geoff@rabidhost.com>
Cc: "Miquel van Smoorenburg" <miquels@cistron.nl>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Nick Andrew" <nick@nick-andrew.net>,
linux-kernel@vger.kernel.org
Subject: Re: New Security Features, Please Comment
Date: Thu, 4 Dec 2008 08:22:09 +0800 [thread overview]
Message-ID: <804dabb00812031622j45fbdc76u5832a469a8a1d82c@mail.gmail.com> (raw)
In-Reply-To: <1228348854.6993.38.camel@lappy.spacevs.com>
On Thu, Dec 4, 2008 at 8:00 AM, Geoffrey McRae <geoff@rabidhost.com> wrote:
>
> The setuid/gid concept in linux is very limited, it would be nice to be
> able to grant programs limited use of setuid, and even go one step
> further, grant programs limited ability to set child uids.
Yes, there can be many other variation on what u have just said, eg,
adding conditions whereby the grant can be used, etc. If u have a
chance to learn a little bit of SELinux, u will know the whole thing
can be very complex, especially the rules and policies configuration.
It is a fine balance between overheads vs performance and usability.
>
> To be completly honest, this is the kind of functionallity I expected to
> already be there, and I was hopeing someone would tell me to RTFM on
> function X that already does this...
>
Yes, I am sure it exists...and more likely than not, it can be very
application specific, and therefore, will be done by the higher-end
application in userspace.
But looking beyond, is there any other OS that may have something
similar? (Windows, or OpenBSD etc?) Not sure for me.
--
Regards,
Peter Teoh
Ernest Hemingway - "Never mistake motion for action."
next prev parent reply other threads:[~2008-12-04 0:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 23:28 Geoffrey McRae
2008-12-03 0:24 ` Geoffrey McRae
2008-12-03 0:53 ` Alan Cox
2008-12-03 1:44 ` Geoffrey McRae
2008-12-03 2:11 ` David Newall
2008-12-03 2:55 ` Valdis.Kletnieks
2008-12-03 4:02 ` Geoffrey McRae
2008-12-03 4:35 ` Peter Teoh
2008-12-03 5:02 ` Geoffrey McRae
2008-12-03 6:54 ` David Newall
2008-12-03 10:29 ` Alan Cox
2008-12-03 12:42 ` Nick Andrew
2008-12-03 12:46 ` Alan Cox
2008-12-03 22:44 ` Geoffrey McRae
2008-12-03 23:08 ` Alan Cox
2008-12-03 23:27 ` Peter Teoh
2008-12-03 23:40 ` Geoffrey McRae
2008-12-04 21:56 ` Valdis.Kletnieks
2008-12-04 22:30 ` Geoffrey McRae
2008-12-05 3:35 ` Valdis.Kletnieks
2008-12-05 3:44 ` Nick Andrew
2008-12-05 3:50 ` Geoffrey McRae
2008-12-05 4:03 ` Valdis.Kletnieks
2008-12-03 23:39 ` Miquel van Smoorenburg
2008-12-04 0:00 ` Geoffrey McRae
2008-12-04 0:22 ` Peter Teoh [this message]
2008-12-04 0:08 ` Alan Cox
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=804dabb00812031622j45fbdc76u5832a469a8a1d82c@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geoff@rabidhost.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=nick@nick-andrew.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®