Bug 858523 - SELinux is preventing /usr/sbin/pwconv from 'write' accesses on the file /tmp/ffijq61m4 (deleted).
Summary: SELinux is preventing /usr/sbin/pwconv from 'write' accesses on the file /tmp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ebcc3032cac031d2abda42bf35d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 02:36 UTC by Mikhail
Modified: 2012-09-23 04:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-20 06:44:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2012-09-19 02:36 UTC, Mikhail 		no flags Details
File: hashmarkername (14 bytes, text/plain)
2012-09-19 02:36 UTC, Mikhail 		no flags Details
File: description (3.65 KB, text/plain)
2012-09-19 02:36 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2012-09-19 02:36:15 UTC 
Additional info:
libreport version: 2.0.12
kernel:         3.6.0-0.rc2.git2.1.fc18.i686
Comment 1 Mikhail 2012-09-19 02:36:17 UTC 
Created attachment 614177 [details]
File: type
Comment 2 Mikhail 2012-09-19 02:36:19 UTC 
Created attachment 614178 [details]
File: hashmarkername
Comment 3 Mikhail 2012-09-19 02:36:22 UTC 
Created attachment 614179 [details]
File: description
Comment 4 Daniel Walsh 2012-09-20 01:13:56 UTC 
Were you doing something with puppet?  When did this happen?
Comment 5 Mikhail 2012-09-20 02:42:17 UTC 
Don't know what is pwconv and when it running.
I am just install Fedora 18 and get this alert after first boot.
Comment 6 Miroslav Grepl 2012-09-20 06:44:34 UTC 
This should be fixed with a newer policy. We added rules to stop transitioning out of anaconda and firstboot which caused these AVC messages.
Comment 7 Mikhail 2012-09-23 04:39:52 UTC 
I was not right, this occurs not with first boot, this occurs when anaconda complete install.
Note You need to log in before you can comment on or make changes to this bug.