mirrors/talos
1
0
Fork 0
mirror of https://github.com/siderolabs/talos.git synced 2025-11-06 03:11:39 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix wrong capability name

Browse Source 
It's CAP_SYS_BOOT, not CAP_BOOT.

Signed-off-by: Florian Klink <flokli@flokli.de>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This commit is contained in:
Florian Klink 2023-07-13 15:59:27 +03:00 committed by Andrey Smirnov
parent 59d7d9344b
commit b84277d7dc
No known key found for this signature in database
GPG Key ID: 7B26396447AB6DFD
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/v1.4/learn-more/process-capabilities.md
View File

@ -9,7 +9,7 @@ Linux defines a set of [process capabilities](https://man7.org/linux/man-pages/m
Talos Linux for security reasons restricts any process from gaining the following capabilities: Talos Linux for security reasons restricts any process from gaining the following capabilities:
* `CAP_SYS_MODULE` (loading kernel modules) * `CAP_SYS_MODULE` (loading kernel modules)
* `CAP_BOOT` (rebooting the system) * `CAP_SYS_BOOT` (rebooting the system)
This means that any process including privileged Kubernetes pods will not be able to get these capabilities. This means that any process including privileged Kubernetes pods will not be able to get these capabilities.

2
website/content/v1.5/learn-more/process-capabilities.md
View File

@ -9,7 +9,7 @@ Linux defines a set of [process capabilities](https://man7.org/linux/man-pages/m
Talos Linux for security reasons restricts any process from gaining the following capabilities: Talos Linux for security reasons restricts any process from gaining the following capabilities:
* `CAP_SYS_MODULE` (loading kernel modules) * `CAP_SYS_MODULE` (loading kernel modules)
* `CAP_BOOT` (rebooting the system) * `CAP_SYS_BOOT` (rebooting the system)
This means that any process including privileged Kubernetes pods will not be able to get these capabilities. This means that any process including privileged Kubernetes pods will not be able to get these capabilities.