From: Russell Coker <rcoker@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: FAM uses seteuid and setegid
Date: Fri, 21 May 2004 03:32:23 +1000 [thread overview]
Message-ID: <200405210332.23918.rcoker@redhat.com> (raw)
In-Reply-To: <1085070739.521.201.camel@moss-spartans.epoch.ncsc.mil>
On Fri, 21 May 2004 02:32, Stephen Smalley <sds@epoch.ncsc.mil> wrote:
> On Thu, 2004-05-20 at 12:24, Luke Kenneth Casson Leighton wrote:
> > > Famd is badly designed for security. There has been talk of replacing
> > > that functionality with other code, the general concept is that for a
> > > local FAM you just have the first process to call it fork off a child
> > > process which executes a famd in the user context, then other processes
> > > with the same UID can connect to the same famd.
> >
> > that's much more sensible.
>
> Yes, but unfortunately it doesn't help with remote FAM usage, which
> isn't uncommon.
We can still use the current version of famd for remote use, it just becomes
an option that does not need to be installed. Previously famd was required
for any fully functional desktop system, which is not what we want.
--
http://apac.redhat.com/disclaimer
See above URL for disclaimer.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2004-05-20 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 12:15 FAM uses seteuid and setegid Luke Kenneth Casson Leighton
2004-05-20 12:42 ` Stephen Smalley
2004-05-20 13:55 ` Luke Kenneth Casson Leighton
2004-05-20 14:27 ` Stephen Smalley
2004-05-20 14:41 ` Stephen Smalley
2004-05-20 15:14 ` Russell Coker
2004-05-20 16:24 ` Luke Kenneth Casson Leighton
2004-05-20 16:32 ` Stephen Smalley
2004-05-20 17:32 ` Russell Coker [this message]
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=200405210332.23918.rcoker@redhat.com \
--to=rcoker@redhat.com \
--cc=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.