Bug 353571
Summary: | /usr/bin/crontab blocked by selinux | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Poelstra <poelstra> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | matt_domsch, orion, sundaram, wwoods |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-31 20:11:26 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: | |||
Bug Depends On: | |||
Bug Blocks: | 235703 |
Description
John Poelstra
2007-10-26 04:31:42 UTC
Fixed in selinux-policy-3.0.8-36.fc8.src.rpm I haven't been able to reproduce this with the new policy update. John, can you quickly confirm whether this update fixes the problem for you? please point me to a download location for the udpated RPM Koji to the rescue http://koji.fedoraproject.org/koji/buildinfo?buildID=22493 still broken doesn't get flagged or alert by setroubleshoot either. # strace crontab -e execve("/usr/bin/crontab", ["crontab", "-e"], [/* 26 vars */]) = -1 EACCES (Permission denied) dup(2) = 3 fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaaaaac8000 lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(3, "strace: exec: Permission denied\n", 32strace: exec: Permission denied ) = 32 close(3) = 0 munmap(0x2aaaaaac8000, 4096) = 0 exit_group(1) = ? confirmed 3.0.8-36 fails for me too. Looking in my audit.log, I see the following type=SELINUX_ERR msg=audit(1193601682.942:777): security_compute_sid: invalid context system_u:system_r:unconfined_crontab_t:s0 for scontext=system_u:system_r:unconfined_t:s0 tcontext=system_u:object_r:crontab_exec_t:s0 tclass=process type=SYSCALL msg=audit(1193601682.942:777): arch=40000003 syscall=11 success=no exit=-13 a0=9dba058 a1=9dbaf08 a2=9dc19b0 a3=0 items=0 ppid=17973 pid=24090 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=pts8 comm="bash" exe="/bin/bash" subj=system_u:system_r:unconfined_t:s0 key=(null) Confirmed this with 3.0.8-38, confirmed fixed in 3.0.8-39. And confirmed with -40 building now still broken with the same error message... running on x86_64 # rpm -qa | grep selinux selinux-policy-targeted-3.0.8-42.fc8 libselinux-2.0.37-1.fc8 libselinux-python-2.0.37-1.fc8 libselinux-2.0.37-1.fc8 selinux-policy-3.0.8-42.fc8 Do I need to relabel or change something to correctly test this? WORKSFORME on a fresh install. Maybe you need to do a "fixfiles restore /var/spool/cron"? Reporter can't test anymore and we can't reproduce the problem. Closing (again). |