All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: FAM uses seteuid and setegid
Date: Thu, 20 May 2004 12:15:38 +0000	[thread overview]
Message-ID: <20040520121538.GA8810@lkcl.net> (raw)

hi,

just taking a look at famd, which uses seteuid and setegid before
going and 'avin a look at files (Cred::Implementation::become_user())

so, famd is designed to "effectively" set its user and group ids,
such that any file access is done as these, whilst still remaining
actually running as root.

... so... what tricks can be done that are equivalent to this?

setfscreatecon doesn't apply because that's presumably for file
creation, and famd does file access not file creation.

setexeccon doesn't apply because there _are_ no relevant exec
calls that occur in famd, and the only forks() and execs()
are to run programs (e.g. "insmod imon").

hum.

-- 
-- 
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
believing that you have actually started a conversation.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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.

             reply	other threads:[~2004-05-20 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 12:15 Luke Kenneth Casson Leighton [this message]
2004-05-20 12:42 ` FAM uses seteuid and setegid 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

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=20040520121538.GA8810@lkcl.net \
    --to=lkcl@lkcl.net \
    --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.