Bug 121217 - console logins have different user context
Summary: console logins have different user context
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: policy   
(Show other bugs)
Version: rawhide
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-19 10:31 UTC by Thomas Molina
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-04-19 15:21:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Thomas Molina 2004-04-19 10:31:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312

Description of problem:
If I rlogin from another computer or open a terminal window in
runlevel five I get a different user context than if I login at a
"normal" console.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. rlogin, get user context
2. login at a console, get sysadm context

    

Actual Results:  During an rlogin (or a terminal window in runlevel 5)
I get:

[root@dad root]# rlogin -l tmolina dad
Password:
Last login: Mon Apr 19 06:23:55 on tty1
[tmolina@dad tmolina]$ id -Z
user_u:user_r:user_t
[tmolina@dad tmolina]$

When I login at a "normal" console I get:
Fedora Core release 1.91 (FC2)
Kernel 2.6.5-1.326 on an i686
 
dad login: tmolina
Password:
Your default context is user_u:sysadm_r:sysadm_t.
 
Do you want to choose a different one? [n]
Last login: Sun Apr 18 19:22:54 on :0
[tmolina@dad tmolina]$ id -Z
user_u:sysadm_r:sysadm_t


Expected Results:  I should get the same context no matter how I log in.

Additional info:

Comment 1 Colin Walters 2004-04-19 15:21:48 UTC
This should be done in the latest policy.


Note You need to log in before you can comment on or make changes to this bug.