All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Hasan Rezaul-CHR010 <CHR010@motorola.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: Attaching multiple user accounts to same home directory...
Date: Thu, 17 Jul 2008 16:19:38 -0400	[thread overview]
Message-ID: <487FA95A.4090601@redhat.com> (raw)
In-Reply-To: <D06FE0A2807BC145B0D38744789D4F5D04BF257F@de01exm68.ds.mot.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hasan Rezaul-CHR010 wrote:
> Hi Dan,
> 
> Given the project deadline and other constraints, upgrading to the new
> toolchain is NOT an option for me  :-(
> 
> Is there anything else at all I can do as far as tweaking policy or
> config to get by this problem ?  Thanks for your help...
> 
> - Rezaul.
> 
> 
No the problem is genhomedircon must be getting confused.  You can look
at the python code and see if you can figure it out.  It must be writing
two sets of contexts for the same homedir.
> -----Original Message-----
> From: Daniel J Walsh [mailto:dwalsh@redhat.com] 
> Sent: Thursday, July 17, 2008 2:52 PM
> To: Hasan Rezaul-CHR010
> Cc: Stephen Smalley; selinux@tycho.nsa.gov
> Subject: Re: Attaching multiple user accounts to same home directory...
> 
> Hasan Rezaul-CHR010 wrote:
>> Hi Dan,
> 
>> I am using Standard Linux 2.6.14.
> 
>> In case you need this info, the SELinux related packages I am using
> are:
>> checkpolicy     1.34.1
>> libselinux      1.34.7
>> libsemanage     1.10.3
>> libsepol        1.16.1
>> policycoreutils 1.34.6
> 
>> - Rezaul.
> 
> 
> Can you upgrade to the newer toolchain?
> 
> I tried to do what you are doing in rawhide and it works fine.
> 
> rpm -q libselinux checkpolicy libsemanage policycoreutils libsepol
> libselinux-2.0.67-4.fc10.x86_64
> libselinux-2.0.67-4.fc10.i386
> checkpolicy-2.0.16-3.fc10.x86_64
> libsemanage-2.0.25-3.fc10.x86_64
> policycoreutils-2.0.52-5.fc10.x86_64
> libsepol-2.0.32-1.fc10.x86_64
> 
> 
>> -----Original Message-----
>> From: Daniel J Walsh [mailto:dwalsh@redhat.com]
>> Sent: Thursday, July 17, 2008 1:57 PM
>> To: Hasan Rezaul-CHR010
>> Cc: Stephen Smalley; selinux@tycho.nsa.gov
>> Subject: Re: Attaching multiple user accounts to same home
> directory...
>> Hasan Rezaul-CHR010 wrote:
>>> Hi All,
>>> Suppose I wanted to have several Linux User Accounts tied to the same
> 
>>> Home Directory, by executing the following:
>>> useradd -g wadm -d /home/admin admin1 useradd -g wadm -d /home/admin 
>>> admin2
>>> And I wanted all these Linux Users to be tied to the same SELinux 
>>> user
>>> (staff_u) as follows:
>>> semanage login -a -s staff_u admin1
>>> semanage login -a -s staff_u admin2
>>> Does SELinux allow this per design ???
>>> Currently I am getting the following errors on my console, which 
>>> somewhat makes sense, considering this is NOT standard practise!
> 
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/.+.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/.*/plugins/nprhapengine\.so.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/.*/plugins/libflashplayer\.so.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.ssh(/.*)?.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.xauth.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.gnupg(/.+)?.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.fonts(/.*)?.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.gconf(d)?(/.*)?.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for 
>>> /home/admin/\.mozilla(/.*)?/plugins/libflashplayer\.so.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.Xauthority.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.fonts/auto(/.*)?.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.config/gtk-.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.fonts\.cache-.*.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.ICEauthority.*.
>>> Inserting powerspanii.ko:
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin.
>>> /etc/selinux/strict/contexts/files/file_contexts: Multiple same 
>>> specifications for /home/admin/\.fonts\.conf.
> 
>>> I was wondering if there is any way I can tweak SELinux config or 
>>> policy to allow  multiple Linux users to share the same home 
>>> directory...without generating all these complaints ?  Thanks in 
>>> advance for your help  :-)
>>> - Rezaul.
> 
>>> --
>>> 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.
>> I think you have confused the tool.  What OS are you doing this on?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkh/qVkACgkQrlYvE4MpobOAHQCcCuluoLZc8d+eYS4M2LndV2W3
j/IAoMjWPXHxiVXIc2sh8Uj66tn2SGBY
=tfCb
-----END PGP SIGNATURE-----

--
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:[~2008-07-17 20:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 22:17 OpenMoko/JFFS2 sestatus difficulties Willis Vandevanter
2008-07-16  0:54 ` KaiGai Kohei
2008-07-16  3:13   ` Justin Mattock
2008-07-16  7:14     ` Russell Coker
2008-07-16  7:47       ` Justin Mattock
2008-07-16 11:56         ` Russell Coker
2008-07-16  5:15   ` Willis Vandevanter
2008-07-16  5:29     ` Yuichi Nakamura
2008-07-18  0:40     ` Mohamed Hassan
2008-07-16 11:56 ` Stephen Smalley
2008-07-16 15:03   ` Justin Mattock
2008-07-16 15:18     ` Stephen Smalley
2008-07-16 16:48       ` Justin Mattock
2008-07-16 16:56         ` Stephen Smalley
2008-07-16 18:21           ` Justin Mattock
2008-07-17 16:42       ` Attaching multiple user accounts to same home directory Hasan Rezaul-CHR010
2008-07-17 18:57         ` Daniel J Walsh
2008-07-17 19:20           ` Hasan Rezaul-CHR010
2008-07-17 19:52             ` Daniel J Walsh
2008-07-17 20:01               ` Hasan Rezaul-CHR010
2008-07-17 20:19                 ` Daniel J Walsh [this message]
2008-07-18 12:31                 ` Stephen Smalley
2010-04-30 20:32             ` Security Context after SSH-ing in Hasan Rezaul-CHR010
2010-05-03 14:52               ` Stephen Smalley

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=487FA95A.4090601@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=CHR010@motorola.com \
    --cc=sds@tycho.nsa.gov \
    --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.