Skip to content

Commit 2cf0203

Browse files
committed
# minor wording changes learning_selinux.md
1 parent 2f70b6b commit 2cf0203

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

docs/guides/security/learning_selinux.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ Before starting, you should know that SELinux is mainly intended for RHEL distri
2121

2222
**SELinux** (Security Enhanced Linux) is a Mandatory Access Control system.
2323

24-
Before the appearance of MAC systems, standard access management security was based on **DAC** (**D**iscretionary **A**ccess **C**ontrol) systems. An application, or a daemon, operated with **UID** or **SUID** (**S**et **O**wner **U**ser **I**d) rights, which made it possible to evaluate permissions (on files, sockets, and other processes...) according to this user. This operation does not sufficiently limit the rights of a program that is corrupted, potentially allowing it to access the subsystems of the operating system.
24+
Before the appearance of MAC systems, standard access management security was based on **DAC** (**D**iscretionary **A**ccess **C**ontrol) systems. An application, or a daemon, operated with **UID** or **SUID** (**S**et **O**wner **U**ser **I**d) rights, which made it possible to evaluate permissions (on files, sockets, and other processes...) according to this user. This operation does not sufficiently limit the rights of a corrupted program, potentially allowing it to access the subsystems of the operating system.
2525

26-
A MAC system reinforces the separation of confidentiality and integrity information in the system to achieve a containment system. The containment system is independent of the traditional rights system and there is no notion of a superuser.
26+
A MAC system reinforces the separation of confidentiality and integrity information to achieve a containment system. The containment system is independent of the traditional rights system and there is no notion of a superuser.
2727

2828
With each system call, the kernel queries SELinux to see if it allows the action to be performed.
2929

@@ -39,15 +39,15 @@ The SELinux security context is defined by the trio **identity**+**role**+**doma
3939

4040
The identity of a user depends directly on his Linux account. An identity is assigned one or more roles, but to each role corresponds to one domain, and only one.
4141

42-
It is according to the domain of the security context (and thus the role) that the rights of a user on a resource are evaluated.
42+
It is according to the domain of the security context (and thus the role) that user's rights on a resource are evaluated.
4343

4444
![SELinux context](../images/selinux_002.png)
4545

46-
The terms "domain" and "type" are similar. Typically "domain" is used when referring to a process, while "type" refers to an object.
46+
The terms "domain" and "type" are similar. Typically "domain" refers to a process, while "type" refers to an object.
4747

4848
The naming convention is: **user_u:role_r:type_t**.
4949

50-
The security context is assigned to a user at the time of his connection, according to his roles. The security context of a file is defined by the `chcon` (**ch**ange **con**text) command, which we will see later in this document.
50+
The security context is assigned to a user during their connection, according to their roles. The security context of a file is defined by the `chcon` (**ch**ange **con**text) command, which we will see later in this document.
5151

5252
Consider the following pieces of the SELinux puzzle:
5353

@@ -64,7 +64,7 @@ The rights of a process depend on its security context.
6464

6565
By default, the security context of the process is defined by the context of the user (identity + role + domain) who launches it.
6666

67-
A domain being a specific type (in the SELinux sense) linked to a process and inherited (normally) from the user who launched it, its rights are expressed in terms of authorization or refusal on types linked to objects:
67+
A domain is a specific type (in the SELinux sense) linked to a process and inherited (normally) from the user who launched it. Its rights are expressed in terms of authorization or refusal on types linked to objects:
6868

6969
A process whose context has security __domain D__ can access objects of __type T__.
7070

@@ -82,7 +82,7 @@ This mechanism is essential since it restricts the rights of a process as much a
8282

8383
## Management
8484

85-
The `semanage` command is used to manage SELinux rules.
85+
The `semanage` command manages SELinux rules.
8686

8787
```
8888
semanage [object_type] [options]
@@ -97,9 +97,9 @@ $ semanage boolean -l
9797
| Options | Observations |
9898
|---------|-------------------|
9999
| -a | Adds an object |
100-
| -d | Delete an object |
101-
| -m | Modify an object |
102-
| -l | List the objects |
100+
| -d | Deletes an object |
101+
| -m | Modifies an object |
102+
| -l | Lists the objects |
103103

104104
The `semanage` command may not be installed by default under Rocky Linux.
105105

@@ -325,8 +325,8 @@ sudo chcon -vR -t httpd_sys_content_t /data/websites/
325325

326326
| Options | Observations |
327327
|----------------|---------------------------------|
328-
| `-v` | Switch into verbose mode |
329-
| `-R` | Apply recursion |
328+
| `-v` | Switches to verbose mode |
329+
| `-R` | Applies recursion |
330330
| `-u`,`-r`,`-t` | Applies to a user, role or type |
331331

332332
The `restorecon` command restores the default security context (the one provided by the rules):

0 commit comments

Comments
 (0)