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.216.207.192
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
/
usr /
share /
doc /
libmcrypt-dev /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
README
1.12
KB
-rw-r--r--
README.key
472
B
-rw-r--r--
README.xtea
550
B
-rw-r--r--
TODO
105
B
-rw-r--r--
changelog.Debian.gz
1.44
KB
-rw-r--r--
copyright
1.52
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.xtea
The xTEA algorithm may not be right implemented. There are two different behaved implementations, because the specification is not clear. I assumed that the C code in the specification is right, so in mcrypt xtea behaves exactly as the code shown in the specification. The different approach is the code in ftp.funet.fi which seems to be more rational than the code in the specification. But since there is no indication of the author of that code I decided not to adopt this version, and I assumed that the C specification is right. Nikos
Close