From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [patch 2/2] namespace: new policy for namespace.init script
Date: Tue, 22 Mar 2011 08:25:52 -0400 [thread overview]
Message-ID: <4D889550.1030803@redhat.com> (raw)
In-Reply-To: <4D876452.4060201@tresys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/21/2011 10:44 AM, Christopher J. PeBenito wrote:
> On 03/03/11 05:44, Miroslav Grepl wrote:
>> http://mgrepl.fedorapeople.org/F15/apps_namespace_p2.patch
>>
>> * adds polydomain attribute for login programs
>
> I'm unsure why this is necessary.
>
>> * namespace.init runs restorecon
>> * make ssh_home_t parent of polyinstantiated directory since
>> pam_namespace.so can be used for ssh
>
> I don't think I follow. Wouldn't the whole home directory be
> polyinstantiated, not just the .ssh dir?
>
>> * make user_tmp_t parent of polyinstantiated directory
>
> This also seems odd.
>
>
Lets examine what is going on. We want to allow the login programs to
populate a newly created directory from /etc/skel with proper labelling.
If the admin puts /etc/skel/.ssh then this directory needs to be
created by namespace.init with ssh_home_t.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk2IlVAACgkQrlYvE4MpobOedACdGyOxOGaCDh0yOB6ZR5Y+H+l3
S2gAn0KznF2knaYqioTEpwy1K0uRtzsX
=x2t/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-22 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 10:44 [refpolicy] [patch 2/2] namespace: new policy for namespace.init script Miroslav Grepl
2011-03-21 14:44 ` Christopher J. PeBenito
2011-03-22 12:25 ` Daniel J Walsh [this message]
2011-03-23 13:39 ` Christopher J. PeBenito
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=4D889550.1030803@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.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 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.