Różnice między wybraną wersją a wersją aktualną.
| — |
security [2017/01/25 08:03] (aktualna) jpiechnik utworzono |
||
|---|---|---|---|
| Linia 1: | Linia 1: | ||
| + | *Wyłączenie SeLinux*\\ | ||
| + | <code> | ||
| + | vi /etc/sysconfig/selinux | ||
| + | # 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 - SELinux is fully disabled. | ||
| + | SELINUX=disabled | ||
| + | |||
| + | </code> | ||
| + | |||
| + | tymczasowo\\ | ||
| + | <code> | ||
| + | echo 0 >/selinux/enforce | ||
| + | </code> | ||
| + | |||
| + | włączenie | ||
| + | <code> | ||
| + | Re-Enabling SELinux | ||
| + | If you've disabled SELinux as in the section above, and you want to enable it again then you've got a bit of work to do. The problem will be that files created or changed when SELinux was disabled won't have the correct file labels on them - if you just reboot in enforcing mode then a lot of stuff won't work properly. | ||
| + | |||
| + | What you need to do is to enable SELinux by editing /etc/selinux/config (for Fedora/RedHat) or by adding selinux=1 to the kernel boot line, then boot into permissive mode, then relabel everything, and then reboot into (or simply switch to) enforcing mode. | ||
| + | |||
| + | After booting into permissive mode, run | ||
| + | fixfiles relabel | ||
| + | |||
| + | Alternatively, in Fedora and RedHat Enterprise Linux you can run | ||
| + | touch /.autorelabel | ||
| + | and reboot or put | ||
| + | autorelabel | ||
| + | on the boot command line - in both cases the file system gets a full relabel early in the boot process. Note that this can take quite some time for systems with a large number of files. | ||
| + | </code> | ||