Bug 458821 - No response to query: Would you like to enter a security context? [N]
Summary: No response to query: Would you like to enter a security context? [N]
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pam
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-12 14:24 UTC by Robert Scheck
Modified: 2008-08-12 17:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-12 17:40:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2008-08-12 14:24:17 UTC
Description of problem:
Since some time, I've the following here in /var/log/secure:

Aug 12 16:16:28 tux sshd[17663]: pam_unix(sshd:session): session opened for user robert by (uid=0)
Aug 12 16:16:28 tux sshd[17663]: pam_selinux(sshd:session): conversation failed
Aug 12 16:16:28 tux sshd[17663]: pam_selinux(sshd:session): No response to query: Would you like to enter a security context? [N]
Aug 12 16:16:28 tux sshd[17663]: pam_selinux(sshd:session): Unable to get valid context for robert
Aug 12 16:16:29 tux sshd[17663]: error: ssh_selinux_setup_pty: security_compute_relabel: Invalid argument

What the hell is this and why does it appear? IMHO this shouldn't be the case.

Version-Release number of selected component (if applicable):
libselinux-2.0.71-1
openssh-5.1p1-2

How reproducible:
Everytime for me, e.g. during SSH login.

Actual results:
Very strange messages in /var/log/secure during SSH login.

Expected results:
No strange messages in /var/log/secure as in the past.

Comment 1 Daniel Walsh 2008-08-12 14:31:30 UTC
Do you have any special options in you /etc/pam.d/sshd

 grep selinux /etc/pam.d/sshd 
# pam_selinux.so close should be the first session rule
session    required     pam_selinux.so close
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session    required     pam_selinux.so open env_params

Comment 2 Robert Scheck 2008-08-12 14:38:33 UTC
Nothing special I would say, grep returns the same for me here:

# pam_selinux.so close should be the first session rule
session    required     pam_selinux.so close
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session    required     pam_selinux.so open env_params

Comment 3 Daniel Walsh 2008-08-12 17:22:40 UTC
What context is sshd running as?

ps -eZ | grep sshd

Comment 4 Robert Scheck 2008-08-12 17:40:43 UTC
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 5995 ? 00:00:00 sshd

ARGS. Something destroyed the SELinux labeling. Sorry for bothering. I'll open
a bug report when I know what destroyed it...


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