Restrict Access to Kernel Message Buffer
Unprivileged access to the kernel syslog can expose sensitive kernel address information. Change-Id: If40f1b883dfde6c7870bf9c463753d037867c9e2 Signed-off-by: zshi <zshi@redhat.com>
This commit is contained in:
parent
e0bd63c826
commit
51c91597fb
@ -56,5 +56,7 @@ outputs:
|
||||
value: 10000
|
||||
kernel.pid_max:
|
||||
value: {get_param: KernelPidMax}
|
||||
kernel.dmesg_restrict:
|
||||
value: 1
|
||||
step_config: |
|
||||
include ::tripleo::profile::base::kernel
|
||||
|
@ -0,0 +1,11 @@
|
||||
---
|
||||
upgrade:
|
||||
- |
|
||||
The kernel.dmesg_restrict is now set to 1 to prevent exposure of sensitive
|
||||
kernel address information with unprivileged access. Deployments that set
|
||||
or depend on values other than 1 for kernel.dmesg_restrict may be affected
|
||||
by upgrading.
|
||||
security:
|
||||
- |
|
||||
Kernel syslog contains sensitive kernel address information, setting
|
||||
kernel.dmesg_restrict to avoid unprivileged access to this information.
|
Loading…
Reference in New Issue
Block a user