Linux ip-172-26-2-223 5.4.0-1018-aws #18-Ubuntu SMP Wed Jun 24 01:15:00 UTC 2020 x86_64
Apache
: 172.26.2.223 | : 18.223.109.25
Cant Read [ /etc/named.conf ]
8.1.13
www
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
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
snap /
lxd /
33246 /
wrappers /
[ HOME SHELL ]
Name
Size
Permission
Action
kmod
842
B
-rwxr-xr-x
nvidia-container-cli
716
B
-rwxr-xr-x
run-host
400
B
-rwxr-xr-x
Delete
Unzip
Zip
${this.title}
Close
Code Editor : nvidia-container-cli
#!/bin/sh # # This is a bit hacky, as we rely on a library names but at the moment, # we don't have any way to distinguish generic mesa-2404 snap from # mesa-2404 snap with NVIDIA drivers connected to it. (At least, I don't know one.) # Let's do this like that for now at least for PoC purpose. # if snapctl is-connected gpu-2404 && [ -f "${SNAP}/gpu-2404-2/usr/lib/x86_64-linux-gnu/libnvidia-ml.so" ] && [ -f "${SNAP}/gpu-2404-2/usr/lib/x86_64-linux-gnu/libcuda.so" ]; then # We have NVIDIA drivers snap connected, let's use it exec nvidia-container-cli.real "$@" else # Set the root path to use NVIDIA libraries from the host exec nvidia-container-cli.real -r /var/lib/snapd/hostfs/ "$@" fi
Close
