Bug 163092
| Summary: | Targeted selinux policy breaks klogin | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Danny Padwa <daniel.padwa> |
| Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.25.4-10.1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-09-15 15:58:29 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: | |||
Oops. I realized that that security context was after I was playing with it. restorecon resets the context to system_u:object_r:krb5_keytab_t, which results in exactly the same client breakage :-( Hunting deeper, I see that the error message looks like:
type=AVC msg=audit(1121199912.580:796215): avc: denied { read } for
pid=3370 comm="klogind" name="krb5.keytab" dev=dm-0 ino=1737116
scontext=system_u:system_r:rlogind_t tcontext=system_u:object_r:krb5_keytab_t
tclass=file
type=SYSCALL msg=audit(1121199912.580:796215): arch=40000003 syscall=5
success=no exit=-13 a0=8c786c0 a1=8000 a2=1b6 a3=8c7b998 items=1 pid=3370
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
comm="klogind" exe="/usr/kerberos/sbin/klogind"
selinux-policy-targeted-1.25.2-4 (In reply to comment #3) > selinux-policy-targeted-1.25.2-4 Still broken in 1.25.3-5 :-( Did you get different avc messages? Slightly different. Looks like it is a lock rather than a read that is
failing.
type=AVC msg=audit(1122403463.197:6409603): avc: denied { lock } for pid=6230
comm="klogind" name="krb5.keytab" dev=dm-0 ino=1737116
scontext=system_u:system_r:rlogind_t tcontext=system_u:object_r:krb5_keytab_t
tclass=file
type=SYSCALL msg=audit(1122403463.197:6409603): arch=40000003 syscall=221
success=no exit=-13 a0=7 a1=e a2=bf8c3cd4 a3=bf8c3cd4 items=0 pid=6230
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
comm="klogind" exe="/usr/kerberos/sbin/klogind"
type=AVC_PATH msg=audit(1122403463.197:6409603): path="/etc/krb5.keytab"
I made a one-line change to policy-20050719.patch from the 1.25.3-5 RPM and it
now works....
padwad-fc4a$ diff policy-20050719.patch policy-20050726.patch
430c430
< +allow rlogind_t krb5_keytab_t:file { getattr read };
---
> +allow rlogind_t krb5_keytab_t:file { getattr read lock };
|
Description of problem: Incoming klogin doesn't work under targeted selinux policy Version-Release number of selected component (if applicable): selinux-policy-targeted-1.25.1-7 How reproducible: Extremely Steps to Reproduce: 1. set up FC4 with selinux-policy-targeted 2. set up klogin (including getting a keytab) 3. try incoming klogin Actual results: Client cannot authenticate Expected results: Client should be able to authenticate Additional info: Interesting thing is that incoming kshell does work. strace reveals that both processes do a open( "/etc/krb5.keytab", O_RDONLY|O_LARGEFILE ) fcntl64( fd, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}, ptr ) The failing klogin gets an error from fcntl64 (and then barfs). The happy ksh gets back a 0. I can attach a full strace output if you want, or SELinux log messages, if you can tell me where to find them The security context on /etc/krb5.keytab is system_u:object_r:krb5_conf_t Setting SELinux to permissive makes incoming klogin work the way it should Looks like klogin needs to be classified more like ksh for SELinux purposes