Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 119320 - su invalidly prompts for security context
su invalidly prompts for security context
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Depends On:
Blocks: 122683
  Show dependency treegraph
Reported: 2004-03-29 09:25 EST by Gene Czarcinski
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-27 10:01:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2004-03-29 09:25:06 EST
Description of problem:
I have two regular (non root) users defined and an admin user too.  I
am loged in as the admin user.  If I try to su to the regular user
   su - genec
I am prompted to see if I want to change the security context (defualt
=y) but nothing entered seems to work.  There are no alternate
contexts defined for this user.

If I use ssh to try and login from another system .. I get in, no prompts.

Per Dan Walsh:

"The ssh behavior is currect.  The only time you should get prompted
for security contexts is if the user has the ability to have more than
one security context."
Comment 1 Gavin Scott 2004-04-01 14:18:01 EST
I had a similar problem, but perhaps worse (you don't mention whether
you were able to log in directly as the two regular users).  

This was immediately after a fresh install of Core2 Test2 onto a clean
partition.  After doing the cd install (with permissive selinux chosen
from the firewall screen) and rebooting, during "first boot"
initialization gui dialogs I set up a new user account.  However when
I went to log in as that user I was unable to.  Investigation revealed
the user hadn't been created.  No entry in /etc/passwd, no directory
in /home.

So I logged in as root and used the gui User admin tool to create the
new user.  This time the user was created.

On trying to log in as that user I would get:

via gdm: popup saying something like "executable context not allowed",
click ok bombs me back to gdm.

via console: same message you received (change security context, tried
entering user_r/user_t, which wasn't accepted).

via su (from root): same security context message

didn't try ssh.


fixfiles relabel

fixed things for me.
Comment 2 Tomas Mraz 2004-11-16 13:41:18 EST
Please try with latest Fedora Core.
Comment 3 Tomas Mraz 2004-12-27 10:01:21 EST
I don't see such problems with FC3 and targeted selinux policy.

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