From: Timo Sirainen Date: Sun, 24 Jan 2010 22:59:34 +0000 (+0200) Subject: auth: Don't use section names for passdb/userdb driver names. X-Git-Tag: 2.0.beta2~41 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9dd1c256910f1fb42823116a641e7edb3ad11970;p=thirdparty%2Fdovecot%2Fcore.git auth: Don't use section names for passdb/userdb driver names. When using section names, it wasn't possible to use the same driver more than once without an error. --HG-- branch : HEAD --- diff --git a/doc/example-config/conf.d/auth.conf b/doc/example-config/conf.d/auth.conf index 6f19742ca5..872a8bd1f3 100644 --- a/doc/example-config/conf.d/auth.conf +++ b/doc/example-config/conf.d/auth.conf @@ -112,19 +112,21 @@ auth_mechanisms = plain # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: -#passdb passwd-file { +#passdb { + #driver = passwd-file # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} -# PAM authentication. Preferred nowadays by most systems. -# Note that PAM can only be used to verify if user's password is correct, -# so it can't be used as userdb. If you don't want to use a separate user -# database (passwd usually), you can use static userdb. -# REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM -# authentication to actually work. -passdb pam { +passdb { + # PAM authentication. Preferred nowadays by most systems. + # Note that PAM can only be used to verify if user's password is correct, + # so it can't be used as userdb. If you don't want to use a separate user + # database (passwd usually), you can use static userdb. + # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM + # authentication to actually work. + driver = pam # [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=] # [cache_key=] [] # @@ -157,61 +159,53 @@ passdb pam { # args = session=yes %Ls # args = cache_key=%u dovecot #args = dovecot -} -# System users (NSS, /etc/passwd, or similiar) -# In many systems nowadays this uses Name Service Switch, which is -# configured in /etc/nsswitch.conf. -#passdb passwd { + # System users (NSS, /etc/passwd, or similiar) + # In many systems nowadays this uses Name Service Switch, which is + # configured in /etc/nsswitch.conf. + #driver = passwd # [blocking=yes] - See userdb passwd for explanation #args = -#} -# Shadow passwords for system users (NSS, /etc/shadow or similiar). -# Deprecated by PAM nowadays. -# -#passdb shadow { + # Shadow passwords for system users (NSS, /etc/shadow or similiar). + # Deprecated by PAM nowadays. + # + #driver = shadow # [blocking=yes] - See userdb passwd for explanation #args = -#} -# PAM-like authentication for OpenBSD. -# -#passdb bsdauth { + # PAM-like authentication for OpenBSD. + # + #driver = bsdauth # [cache_key=] - See cache_key in PAM for explanation. #args = -#} -# passwd-like file with specified location -# -#passdb passwd-file { + # passwd-like file with specified location + # + #driver = passwd-file # [scheme=] [username_format=] # #args = -#} -# checkpassword executable authentication -# NOTE: You will probably want to use "userdb prefetch" with this. -# -#passdb checkpassword { + # checkpassword executable authentication + # NOTE: You will probably want to use "userdb prefetch" with this. + # + #driver = checkpassword # Path for checkpassword binary #args = -#} -# SQL database -#passdb sql { + # SQL database + #driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext #args = -#} -# LDAP database -#passdb ldap { + # LDAP database + #driver = ldap # Path for LDAP configuration file, see example-config/dovecot-ldap.conf.ext #args = -#} -# vpopmail authentication -#passdb vpopmail { + # vpopmail authentication + #driver = vpopmail # [cache_key=] - See cache_key in PAM for explanation. # [quota_template=