Bug 1312570 - [Security] SELinux troubleshoot instructions outdated for journalctl
[Security] SELinux troubleshoot instructions outdated for journalctl
Product: Fedora
Classification: Fedora
Component: selinux-doc (Show other bugs)
All Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-27 07:20 EST by Jean-Christophe Baptiste
Modified: 2016-12-20 14:04 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 14:04:06 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jean-Christophe Baptiste 2016-02-27 07:20:03 EST
Description of problem:

SELinux troubleshooting instruction provided with (at least) Fedora 23 are outdated.

They are not compatible with journalctl when it comes to adjust the policy.

Not fixing this issue may lead to a lot of bug reporting noise and confusion with security-wise wrong solutions, as illustrated in this bug related to Firefox/Thunderbird plugins accesses: 


Probably many users end up disabling SELinux or applying dangerous unconfined tags.

How reproducible:

Steps to Reproduce:

Just get any SELinux alert and follow the instruction to adjust the system policy.

Outdated instructions look like that :

# grep npviewer.bin /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Actual results:

If you apply the recommended instruction, of course, nothing happens.
Because of stdout piping, it leads to a silent error, but the grep command fails as now logs are in binary format :

# grep npviewer.bin /var/log/audit/audit.log                       
Fichier binaire /var/log/audit/audit.log correspondant

Expected results:

SELinux is not an easy beast, so instructions should be clear and straightforward, so that false-positive don't trigger all the time.

Instead, a command compatible with journalctl would look like that (could probably be improved):

# journalctl  | grep -i "denied.*npviewer" | head -n 1 | audit2allow -M mypol
# semodule -i mypol.pp
Comment 1 Fedora End Of Life 2016-11-24 10:47:39 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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 2 Fedora End Of Life 2016-12-20 14:04:06 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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