Bug 454560

Summary:	SELinux denied access requested by acroread. It is not expected that this access is required by acroread and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to...
Product:	[Fedora] Fedora	Reporter:	Philip Ogunbona <pogna>
Component:	selinux-policy	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	jkubin, spike85051
Target Milestone:	---
Target Release:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-08 19:38:10 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:

Description Philip Ogunbona 2008-07-08 23:44:25 UTC

Description of problem:

SELinux denied access requested by acroread. It is not expected that this access
is required by acroread and this access may signal an intrusion attempt. It is
also possible that the specific version or configuration of the application is
causing it to require additional access.  
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2008-08-01 15:14:29 UTC

Please attach entire setroubleshoot message or the AVC that is being reported
from /var/log/audit/audit.log

Comment 2 Philip Ogunbona 2008-08-02 20:16:37 UTC

The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

SELinux denied access requested by acroread. It is not expected that this access is required by acroread and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access.

Comment 3 Daniel Walsh 2008-09-08 19:38:10 UTC

You never attached the audit log so I am closing for lack of information.

If you still have this problem and have the audit log or the setroubleshoot message please attach the information.