From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <538486E0.4030506@tresys.com> Date: Tue, 27 May 2014 08:36:48 -0400 From: "Christopher J. PeBenito" MIME-Version: 1.0 To: Stephen Smalley , Dominick Grift , dE Subject: Re: Significance of SELinux user and roles on objects. References: <537AE191.7070403@gmail.com> <537B5BD3.4090507@tresys.com> <537D9F47.7020704@gmail.com> <1400743958.10370.0.camel@x220.localdomain> <537F5039.5070806@tycho.nsa.gov> In-Reply-To: <537F5039.5070806@tycho.nsa.gov> Content-Type: text/plain; charset="ISO-8859-1" Cc: selinux@tycho.nsa.gov List-Id: "Security-Enhanced Linux \(SELinux\) mailing list" List-Post: List-Help: On 05/23/2014 09:42 AM, Stephen Smalley wrote: > On 05/22/2014 03:32 AM, Dominick Grift wrote: >> On Thu, 2014-05-22 at 12:25 +0530, dE wrote: >>> On 05/20/14 19:12, Christopher J. PeBenito wrote: >>>> The kernel will create files with object_r regardless >>> >>> Is this defined in the policy or is hard coded in the kernel? >> >> Hard coded into the kernel > > Unless the policy specifies to default from source or target for the > file class... So if I explicitly put default_role from target it will start inheriting the directory's role? If so, did that change also fix role_transition to work on file creation? i.e. can I write a rule like: role_transition user_r tmp_t:file user_r; So I can get the default_role from source-like behavior on certain types (I'd like to bring back role separations in refpolicy)? -- Chris PeBenito Tresys Technology, LLC www.tresys.com | oss.tresys.com