Linux tsuru-no-tsurugi 5.15.0-186-generic #196-Ubuntu SMP Sat Jun 20 16:09:34 UTC 2026 x86_64
Apache/2.4.52 (Ubuntu)
Server IP : 192.168.0.18 & Your IP : 216.73.216.68
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
snap /
core20 /
2866 /
etc /
sysctl.d /
Delete
Unzip
Name
Size
Permission
Date
Action
10-console-messages.conf
77
B
-rw-r--r--
2020-02-27 14:52
10-ipv6-privacy.conf
490
B
-rw-r--r--
2020-02-27 14:52
10-kernel-hardening.conf
726
B
-rw-r--r--
2020-02-27 14:52
10-link-restrictions.conf
257
B
-rw-r--r--
2020-02-27 14:52
10-magic-sysrq.conf
1.16
KB
-rw-r--r--
2020-02-27 14:52
10-network-security.conf
158
B
-rw-r--r--
2020-02-27 14:52
10-ptrace.conf
1.26
KB
-rw-r--r--
2020-02-27 14:52
10-zeropage.conf
506
B
-rw-r--r--
2020-02-27 14:52
README.sysctl
792
B
-rw-r--r--
2020-02-14 07:44
Save
Rename
# 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