Bug 23873 - SELinux won't enable when using setenforce
Summary: SELinux won't enable when using setenforce
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 10:38 CET by Anthony BILLETTE
Modified: 2018-11-22 04:19 CET (History)
1 user (show)

See Also:
Source RPM: kernel-4.14.78-1.mga6.src.rpm
CVE:
Status comment:

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

Description Anthony BILLETTE 2018-11-21 10:38:31 CET 
Description of problem:
I don't arrive activated selinux in order to use it to secure my centenary docker


Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-7.mga6.noarch.rpm
mageia:6


Steps to Reproduce:
1. su -
2. urpmi selinux-policy
3. setenforce  1
SELinux is disabled
4. setenforce 0
SELinux is disabled

I can't use selinux on mageia because it is not possible to activate it. I thank you in advance.
Comment 1 David Walser 2018-11-22 04:05:56 CET 
Indeed, SELinux isn't supported in Mageia.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 2 Neal Gompa 2018-11-22 04:19:28 CET 
Adjusting the bug report to make it clearer what the issue was.

The fundamental issue is caused by the kernel, so marking that as the correct source RPM.

If you'd like to request SELinux to be enabled, please file a bug report for Cauldron for this.

CC: (none) => ngompa13
URL: https://mageia.pkgs.org/6/mageia-core-release-x86_64/selinux-policy-3.13.1-7.mga6.noarch.rpm.html => (none)
Summary: SELinux can't activated it => SELinux won't enable when using setenforce
Source RPM: https://mageia.pkgs.org/6/mageia-core-release-x86_64/selinux-policy-3.13.1-7.mga6.noarch.rpm.html => kernel-4.14.78-1.mga6.src.rpm

Neal Gompa 2018-11-22 04:19:52 CET

Component: Installer => RPM Packages
Note You need to log in before you can comment on or make changes to this bug.