SELinux status：disabled

[15day]

root@s32g274aevb:# sestatus
SELinux status: disabled
root@s32g274aevb:# cat /etc/selinux/config

This file controls the state of SELinux on the system.

SELINUX= can take one of these three values:

enforcing - SELinux security policy is enforced.

permissive - SELinux prints warnings instead of enforcing.

disabled - No SELinux policy is loaded.

SELINUX=permissive

SELINUXTYPE= can take one of these values:

minimum - Minimum Security protection.

standard - Standard Security protection.

mls - Multi Level Security protection.

targeted - Targeted processes are protected.

mcs - Multi Category Security protection.

SELINUXTYPE=minimum
root@s32g274aevb:~# setenforce 1
setenforce: SELinux is disabled

My question:Why can't I enable selinux correctly

[bachradsusi]

15day ***@***.***> writes:

15day created an issue (SELinuxProject/selinux#480) ***@***.***:~# sestatus SELinux status: disabled ***@***.***:~# cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=permissive # SELINUXTYPE= can take one of these values: # minimum - Minimum Security protection. # standard - Standard Security protection. # mls - Multi Level Security protection. # targeted - Targeted processes are protected. # mcs - Multi Category Security protection. SELINUXTYPE=minimum ***@***.***:~# setenforce 1 setenforce: SELinux is disabled My question:Why can't I enable selinux correctly

https://docs.fedoraproject.org/en-US/quick-docs/selinux-changing-states-and-modes/#_enabling_selinux Quote: Procedure If your system has SELinux disabled at the kernel level (this is the recommended way, see Disabling SELinux), change this first. Check if you have the selinux=0 option in your kernel command line: $ cat /proc/cmdline BOOT_IMAGE=... ... selinux=0 Remove the selinux=0 option from the bootloader configuration using grubby: $ sudo grubby --update-kernel ALL --remove-args selinux The change applies after you restart the system in one of the following steps. ...

[15day]

I generated the linux image through yocto. grubby cannot be installed on the arm platform。
helong@helong-virtual-machine:~/sources/fsl-auto-yocto-bsp/build_s32g274aevb$ bitbake grubby
Loading cache: 100% |####################################################################| Time: 0:00:03
Loaded 5429 entries from dependency cache.
Parsing recipes: 100% |##################################################################| Time: 0:00:04
Parsing of 3613 .bb files complete (3612 cached, 1 parsed). 5432 targets, 599 skipped, 2 masked, 0 errors.
ERROR: Nothing PROVIDES 'grubby'
grubby was skipped: incompatible with host aarch64-fsl-linux (not in COMPATIBLE_HOST)

Summary: There was 1 ERROR message, returning a non-zero exit code.