Linux polon 4.19.0-27-amd64 #1 SMP Debian 4.19.316-1 (2024-06-25) x86_64
Apache/2.4.59 (Debian)
: 10.2.73.233 | : 18.117.91.116
Cant Read [ /etc/named.conf ]
5.6.40-64+0~20230107.71+debian10~1.gbp673146
www-data
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
etc /
systemd /
system /
sysinit.target.wants /
[ HOME SHELL ]
Name
Size
Permission
Action
apparmor.service
1.13
KB
-rw-r--r--
keyboard-setup.service
287
B
-rw-r--r--
systemd-timesyncd.service
1.4
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : apparmor.service
[Unit] Description=Load AppArmor profiles DefaultDependencies=no Before=sysinit.target After=local-fs.target After=systemd-journald-audit.socket RequiresMountsFor=/var/cache/apparmor AssertPathIsReadWrite=/sys/kernel/security/apparmor/.load ConditionSecurity=apparmor Documentation=man:apparmor(7) Documentation=https://gitlab.com/apparmor/apparmor/wikis/home/ # Don't start this unit on the Ubuntu Live CD ConditionPathExists=!/rofs/etc/apparmor.d # Don't start this unit on the Debian Live CD when using overlayfs ConditionPathExists=!/run/live/overlay/work [Service] Type=oneshot ExecStart=/lib/apparmor/apparmor.systemd reload ExecReload=/lib/apparmor/apparmor.systemd reload # systemd maps 'restart' to 'stop; start' which means removing AppArmor confinement # from running processes (and not being able to re-apply it later). # Upstream systemd developers refused to implement an option that allows overriding # this behaviour, therefore we have to make ExecStop a no-op to error out on the # safe side. # # If you really want to unload all AppArmor profiles, run aa-teardown ExecStop=/bin/true RemainAfterExit=yes [Install] WantedBy=sysinit.target
Close