Voici quelques elements de mes tests
[code]testsaslauthd -u xxx@xxxxxx.xx.xx -p xxxxx -f /var/spool/postfix/var/run/saslauthd/mux
0: NO “authentication failed”
testsaslauthd -u xxx@xxxxxx.xx.xx -p xxxxx
connect() : No such file or directory
[/code]
Le contenu de /etc/default/saslauthd
[code]#
Settings for saslauthd daemon
Please read /usr/share/doc/sasl2-bin/README.Debian for details.
Should saslauthd run automatically on startup? (default: no)
START=yes
Description of this saslauthd instance. Recommended.
(suggestion: SASL Authentication Daemon)
DESC=“SASL Authentication Daemon”
Short name of this saslauthd instance. Strongly recommended.
(suggestion: saslauthd)
NAME=“saslauthd”
Which authentication mechanisms should saslauthd use? (default: pam)
Available options in this Debian package:
getpwent – use the getpwent() library function
kerberos5 – use Kerberos 5
pam – use PAM
rimap – use a remote IMAP server
shadow – use the local shadow password file
sasldb – use the local sasldb database file
ldap – use LDAP (configuration is in /etc/saslauthd.conf)
Only one option may be used at a time. See the saslauthd man page
for more information.
Example: MECHANISMS=“pam”
MECHANISMS=“pam”
Additional options for this mechanism. (default: none)
See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""
How many saslauthd processes should we run? (default: 5)
A value of 0 will fork a new process for each connection.
THREADS=5
Other options (default: -c -m /var/run/saslauthd)
Note: You MUST specify the -m option or saslauthd won’t run!
WARNING: DO NOT SPECIFY THE -d OPTION.
The -d option will cause saslauthd to run in the foreground instead of as
a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
to run saslauthd in debug mode, please run it by hand to be safe.
See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
See the saslauthd man page and the output of ‘saslauthd -h’ for general
information about these options.
Example for postfix users: “-c -m /var/spool/postfix/var/run/saslauthd”
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
[/code]
Ce que je n’arrive pas a comprendre, c’est pourquoi même avec le socket, la connexion est refusé.
Le compte utilisé par saslauthd pour mysql est pourtant le bon.
Je remarque d’ailleur l’existance d’un fichier pam-mysql.conf dans /etc, mais le contenu aussi inutilisable soit-il est le même que sur le serveur précédant.
D’ailleurs l’authentification SSL IMAP fonctionne elle.
