Bug 435120 - /usr/bin/Xorg (xdm_xserver_t) "read write"
Summary: /usr/bin/Xorg (xdm_xserver_t) "read write"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-27 14:30 UTC by Shocky Han
Modified: 2008-11-17 22:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-17 22:03:12 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shocky Han 2008-02-27 14:30:33 UTC 
소스 문맥:  system_u:system_r:xdm_xserver_t:s0-s0:c0.c1023
대상 문맥:  system_u:object_r:device_t:s0
대상 객체:  None [ chr_file ]
영향을 받은 RPM 패키지:  xorg-x11-server-Xorg-1.3.0.0-33.fc8 [application]
정책 RPM:  selinux-policy-3.0.8-44.fc8
Selinux 활성화:  True
정책 유형:  targeted
MLS 활성화:  True
강제 모드:  Permissive
플러그인명:  plugins.device
호스트명:  fc8live.srpartners.co.kr
플랫폼:  Linux fc8live.srpartners.co.kr 2.6.23.1-42.fc8 #1 SMP Tue Oct 30
13:55:12 EDT 2007 i686 i686
통지 카운트:  18
First Seen:  2008년 01월 29일 (화) 오전 06시 49분 51초
Last Seen:  2008년 02월 27일 (수) 오후 09시 07분 11초
Local ID:  f00f18e4-f227-46e3-afc2-9d4af1860f96
줄 번호:  

원 감사 메세지 :

avc: denied { read write } for comm=X dev=tmpfs egid=0 euid=0 exe=/usr/bin/Xorg
exit=7 fsgid=0 fsuid=0 gid=0 items=0 name=vboxadd pid=2254
scontext=system_u:system_r:xdm_xserver_t:s0-s0:c0.c1023 sgid=0
subj=system_u:system_r:xdm_xserver_t:s0-s0:c0.c1023 suid=0 tclass=chr_file
tcontext=system_u:object_r:device_t:s0 tty=tty7 uid=0
Comment 1 Daniel Walsh 2008-02-27 22:13:04 UTC 
You can allow this for now by executing 

# audit2allow -M mypol -i /var/log/audit/audit.log 
# semodule -i mypol.pp

Fixed in selinux-policy-3.0.8-90.fc8
Comment 2 Daniel Walsh 2008-11-17 22:03:12 UTC 
Closing all bugs that have been in modified for over a month.  Please reopen if the bug is not actually fixed.
Note You need to log in before you can comment on or make changes to this bug.