Bug 142182

Summary: system id is not as defined in faq
Product: [Fedora] Fedora Reporter: Rahul Sundaram <rahulsundaram>
Component: selinux-docAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: kwade
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://fedora.redhat.com/docs/selinux-faq-fc3/
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:07:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 118757    

Description Rahul Sundaram 2004-12-07 22:49:48 UTC
Description of problem:


id -Z returns security context different from the faq


Steps to Reproduce:
1.switching to root user using su - root and typing id -Z returns
  
Actual results:
root:system_r:unconfined_t

Expected results:

I believe the results are correct because adding users gives the
expected security context as mentioned in the faq

Additional info:

1.3 resolving problems How can I create a new Linux user account with
the user's home directory having the proper context?
A:. 	

You can create your new user with the standard useradd command, but
first you must become root with a context of sysadm_r. This context
switch has been incorporated into the su command and occurs automatically:

su - root
id -Z
root:sysadm_r:sysadm_t"
              ^^^^^^^^

#id -Z
root:system_r:unconfined_t

This is actually unconfined_t under the default targetted policy in fc3

adding users works correctly

drwx------  auser    auser    root:object_r:user_home_dir_t    auser

Comment 1 Karsten Wade 2004-12-20 21:53:15 UTC
Hope to get to these updates soon.  

*** This bug has been marked as a duplicate of 139433 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:07:36 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.