OXIESEC PANEL
- Current Dir:
/
/
snap
/
core20
/
2599
/
etc
/
sysctl.d
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
05/26/2025 10:13:33 PM
rwxr-xr-x
📄
10-console-messages.conf
77 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-ipv6-privacy.conf
490 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-kernel-hardening.conf
726 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-link-restrictions.conf
257 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-magic-sysrq.conf
1.16 KB
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-network-security.conf
158 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-ptrace.conf
1.26 KB
02/27/2020 05:52:07 AM
rw-r--r--
📄
10-zeropage.conf
506 bytes
02/27/2020 05:52:07 AM
rw-r--r--
📄
README.sysctl
792 bytes
02/13/2020 10:44:31 PM
rw-r--r--
Editing: 10-kernel-hardening.conf
Close
# These settings are specific to hardening the kernel itself from attack # from userspace, rather than protecting userspace from other malicious # userspace things. # # # When an attacker is trying to exploit the local kernel, it is often # helpful to be able to examine where in memory the kernel, modules, # and data structures live. As such, kernel addresses should be treated # as sensitive information. # # Many files and interfaces contain these addresses (e.g. /proc/kallsyms, # /proc/modules, etc), and this setting can censor the addresses. A value # of "0" allows all users to see the kernel addresses. A value of "1" # limits visibility to the root user, and "2" blocks even the root user. kernel.kptr_restrict = 1