> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/operations/selinux-management.md).

# SELinux management

Managing SELinux on a TelcoBridges host: checking the current status, and changing enforcement mode permanently or for the current session.

### How to get SELinux status

The following command will retreive the SELinux status of your system (output may vary):

```
sestatus
```

exemple from CentOS 5.3

```
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: permissive
Policy version: 21
Policy from config file: targeted
```

### How to disable SELinux

#### Set SELinux to permissive (not truly disabled)

```
setenforce 0
```

#### Disable SELinux entirely

Edit the file:

```
vi /etc/selinux/config
```

Set the line to SELINUX=disabled

1. This file controls the state of SELinux on the system.
2. SELINUX= can take one of these three values:
3. enforcing - SELinux security policy is enforced.
4. permissive - SELinux prints warnings instead of enforcing.
5. disabled - SELinux is fully disabled. SELINUX=disabled <------ Line to modify
6. SELINUXTYPE= type of policy in use. Possible values are:
7. targeted - Only targeted network daemons are protected.
8. strict - Full SELinux protection. SELINUXTYPE=targeted

Reboot or use the setenforce command:

```
shutdown -r now
or
setenforce 0
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/other-pages/operations/selinux-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.