Bug 881339 - AVCs on boot with unconfined off
Summary: AVCs on boot with unconfined off
Keywords:
Status: CLOSED DUPLICATE of bug 881491
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-28 18:23 UTC by Robin Powell
Modified: 2013-07-07 07:20 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-07 07:20:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
AVCs on boot (7.25 KB, text/plain)
2012-11-28 18:27 UTC, Robin Powell
no flags Details

Description Robin Powell 2012-11-28 18:23:56 UTC
I just upgraded this system, and I *just* ran "fixfiles onboot" (with "rw enforcing=0" as kernel options, because in ro it doesn't work at all and in enforcing mode there were some errors).  See attached.

-Robin

Comment 1 Robin Powell 2012-11-28 18:27:07 UTC
Created attachment 653654 [details]
AVCs on boot

Comment 2 Miroslav Grepl 2012-11-29 07:14:24 UTC
Any idea why jockey needs mknod capability? Do you know which a special file is created?

Comment 3 Robin Powell 2012-11-29 11:14:52 UTC
I'm confused; I don't know what jockey is, and I don't see anything about mknod in what I posted.

-Robin

Comment 4 Daniel Walsh 2012-11-30 05:03:58 UTC
He is asking about a different bugzilla.


It looks like /home directory is mislabeled.

restorecon -R -v /home

Should fix, Did the machine relabel at boot?

Comment 5 Miroslav Grepl 2012-11-30 07:10:53 UTC
(In reply to comment #3)
> I'm confused; I don't know what jockey is, and I don't see anything about
> mknod in what I posted.
> 
> -Robin

Ah I apologize. Yes it was for a different bugzilla.

Comment 6 Robin Powell 2012-12-02 19:45:47 UTC
Daniel: As I said in the initial comment, it had just done a complete relabel.

Running the restorecon did nothing interesting.

I can't reboot any time soon to test it, though.  -_-  Sorry about that.

If it's not freaking you guys out, feel free to close, it was just an FYI.

-Robin

Comment 7 Fedora End Of Life 2013-07-04 00:53:41 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Miroslav Grepl 2013-07-07 07:20:10 UTC

*** This bug has been marked as a duplicate of bug 881491 ***


Note You need to log in before you can comment on or make changes to this bug.