All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janak Desai <janak@us.ibm.com>
To: Russell Coker <russell@coker.com.au>,
	tmraz@redhat.com, sds@tycho.nsa.gov, valdis.kletnieks@vt.edu
Cc: serue@us.ibm.com, klaus@atsec.com, selinux@tycho.nsa.gov
Subject: pam_namespace improvements ..
Date: Sun, 21 May 2006 20:48:00 -0400	[thread overview]
Message-ID: <44710A40.4060309@us.ibm.com> (raw)


Hi Russell,

After going thorugh the pam_namespace thread again and after talking to
some of my peeps, I do see that a mode 000 instance parent can thwart
attacks by non-root daemons and non-polyinstanted users on polyinstanted
users.

The current implementation of pam_namespace already depends on the
existance of the instance parent and allows the admin to configure the names
of different instances. I will update the namespace.conf man page, and
the comment text in the namespace.conf file to guide admins to
appropriately create a different instance parent (and not use the poly
dir itself, like the current example suggests). That way, an admin can
create an intermediate directory like .inst with 000 or create a whole
different directory with 000.

Thanks.

-Janak



--
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:[~2006-05-22  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  0:48 Janak Desai [this message]
2006-05-22  1:05 ` pam_namespace improvements Russell Coker
2006-05-22 13:18   ` Janak Desai
2006-05-31 21:32     ` [PATCH] pam_namespace : option to check instance parent mode and man page(s) updates Janak Desai
     [not found]       ` <1149167654.3514.16.camel@perun.kabelta.loc>
2006-06-01 15:33         ` Janak Desai
2006-06-01 16:52       ` [PATCH] pam_namespace : option to check instance parent mode and man page(s) updates - v2 Janak Desai

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=44710A40.4060309@us.ibm.com \
    --to=janak@us.ibm.com \
    --cc=klaus@atsec.com \
    --cc=russell@coker.com.au \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=serue@us.ibm.com \
    --cc=tmraz@redhat.com \
    --cc=valdis.kletnieks@vt.edu \
    /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.