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
# The PTRACE system is used for debugging. With it, a single user process # can attach to any other dumpable process owned by the same user. In the # case of malicious software, it is possible to use PTRACE to access # credentials that exist in memory (re-using existing SSH connections, # extracting GPG agent information, etc). # # A PTRACE scope of "0" is the more permissive mode. A scope of "1" limits # PTRACE only to direct child processes (e.g. "gdb name-of-program" and # "strace -f name-of-program" work, but gdb's "attach" and "strace -fp $PID" # do not). The PTRACE scope is ignored when a user has CAP_SYS_PTRACE, so # "sudo strace -fp $PID" will work as before. For more details see: # https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#ptrace # # For applications launching crash handlers that need PTRACE, exceptions can # be registered by the debugee by declaring in the segfault handler # specifically which process will be using PTRACE on the debugee: # prctl(PR_SET_PTRACER, debugger_pid, 0, 0, 0); # # In general, PTRACE is not needed for the average running Ubuntu system. # To that end, the default is to set the PTRACE scope to "1". This value # may not be appropriate for developers or servers with only admin accounts. kernel.yama.ptrace_scope = 1