Bug 132985 - Could not get current context for /dev/tty1
Could not get current context for /dev/tty1
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks: FC3Target
  Show dependency treegraph
 
Reported: 2004-09-20 13:03 EDT by Brian Millett
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-20 15:43:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Brian Millett 2004-09-20 13:03:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040904 Firefox/0.9.3

Description of problem:
with selinuxtype set to targeted, I get a strange warning when I go to
a tty[1-9]

Fedora Core release Rawhide (Rawhide)
Kernel 2.6.8-1.549 on an i686

indoffcallacctg login: root
Password:
login(pam_unix)[3770]: session opened for user root by (uid=0)
login[3770]: Warning!  Could not get current context for /dev/tty1,
not relabeling.
Last login: Mon Sep 20 11:25:06 on tty1
 -- root[3770]: ROOT LOGIN ON tty1



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


How reproducible:
Always

Steps to Reproduce:
1.enable selinuxtype-targeted
2.boot
3.go to a tty[1-9] and login
    

Actual Results:  login(pam_unix)[3770]: session opened for user root
by (uid=0)
login[3770]: Warning!  Could not get current context for /dev/tty1,
not relabeling.
Last login: Mon Sep 20 11:25:06 on tty1

Expected Results:  simple login

Additional info:
Comment 1 Brian Millett 2004-09-20 15:43:37 EDT
this was resolved by using the -1.541 kernel.  The kernel I was using
from Arjan did not have the xattr patch.

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