OXIESEC PANEL
- Current Dir:
/
/
snap
/
core
/
17210
/
etc
/
sysctl.d
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
10/02/2024 07:52:55 PM
rwxr-xr-x
📄
10-console-messages.conf
77 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-ipv6-privacy.conf
490 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-kernel-hardening.conf
726 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-link-restrictions.conf
257 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-magic-sysrq.conf
1.16 KB
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-network-security.conf
509 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-ptrace.conf
1.26 KB
01/13/2016 11:48:55 AM
rw-r--r--
📄
10-zeropage.conf
506 bytes
01/13/2016 11:48:55 AM
rw-r--r--
📄
99-sysctl.conf
2.19 KB
10/02/2024 07:51:17 PM
rw-r--r--
📄
README
519 bytes
01/13/2016 11:48:55 AM
rw-r--r--
Editing: 10-magic-sysrq.conf
Close
# The magic SysRq key enables certain keyboard combinations to be # interpreted by the kernel to help with debugging. The kernel will respond # to these keys regardless of the current running applications. # # In general, the magic SysRq key is not needed for the average Ubuntu # system, and having it enabled by default can lead to security issues on # the console such as being able to dump memory or to kill arbitrary # processes including the running screen lock. # # Here is the list of possible values: # 0 - disable sysrq completely # 1 - enable all functions of sysrq # >1 - enable certain functions by adding up the following values: # 2 - enable control of console logging level # 4 - enable control of keyboard (SAK, unraw) # 8 - enable debugging dumps of processes etc. # 16 - enable sync command # 32 - enable remount read-only # 64 - enable signalling of processes (term, kill, oom-kill) # 128 - allow reboot/poweroff # 256 - allow nicing of all RT tasks # # For example, to enable both control of console logging level and # debugging dumps of processes: kernel.sysrq = 10 # kernel.sysrq = 176