search for: digest_md5

...king out very well right now. It seems I can only do plaintext authentication. I got stuck on the userdb/auth_passdb settings. Can someone give me an example of how to configure for md5-digest authentication? My current guess is: disable_plaintext_auth = yes auth = digest-md5 auth_mechanism = digest_md5 auth_passdb = /etc/mydigestfile How would I set this for pgsql? auth_passdb = /etc/dovecot-pgsql.conf ### non-default config settings. protocols = imap imaps disable_plaintext_auth = yes login = imap login_max_processes_count = 16 login = pop3 max_mail_processes = 512 default_mail_env = maild...

...led. 5 logout * BYE Logging out 5 OK Logout completed. hmm no unsupported authentication mechanism. So that means all authentication methods works right? ;-) looking a little further into the configuration, I see instructions to change auth_methods to add plain in front of digest-md5 (or is it digest_md5, both forms are present in the configuration file). No luck. Doing so gives me the following error message: Fatal: Error in configuration file /usr/local/etc/dovecot.conf line 430: Unknown setting: methods so, I'm not sure what to look for. It's probably something simple but googlin...

Good day, I am having trouble getting dovecot to authenticate using postgresql. For some reason, it fails on a PAM error, although I have specified pgsql as authentication? Here my setups: dovecot.conf: -- snip-- (not sure if you need teh rest) auth = digest_md5 auth_mechanisms = plain digest-md5 auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf auth_user = root dovecot-pgsql.conf: connect = host=localhost dbname=postfix user=postfix password=postfix default_pass_scheme = MD5 password_query = SELECT password FROM mail...

Hi All, I am trying to build libvirt from source, the compilation went fine and I see that various libvirt tools are being generated, but when I try to use the generated virsh with qemu and ssh (example virsh qemu+ssh://uri/system) I am not able to login and it fails with the following error: error: failed to connect to the hypervisor error: End of file while reading data: : Input/output error

..._with_hardlinks = no maildir_check_content_changes = no overwrite_incompatible_index = yes umask = 0077 auth = default auth_methods = plain #auth_realms = auth_userinfo = shadow auth_executable = /usr/local/lib/dovecot/imap-auth auth_user = root auth_chroot = /var/run/dovecot auth_count = 1 #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userinfo = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = /var/run/dovecot/auth

...ie.bio2.RWTH-Aachen.DE[134.130.63.5] Apr 20 18:35:03 bert postfix/smtpd[2525]: disconnect from ernie.bio2.RWTH-Aachen.DE[134.130.63.5] Apr 20 18:35:03 bert postfix/smtpd[2525]: master_notify: status 1 my configuration is sasl2/smtp.conf : pwcheck_method: saslauthd mech_list: PLAIN LOGIN CRAM_MD5 DIGEST_MD5 log_level: 6 smb.conf: [global] workgroup = Biologie2 netbios name = bert server string = bert security = DOMAIN log file = /var/log/samba/log.%m max log size = 50 load printers = No os level = 20 interfaces = dc0 bind interfaces only = yes winbind uid = 10000-20000 winbind cache time = 10 templa...

...ie.bio2.RWTH-Aachen.DE[134.130.63.5] Apr 20 18:35:03 bert postfix/smtpd[2525]: disconnect from ernie.bio2.RWTH-Aachen.DE[134.130.63.5] Apr 20 18:35:03 bert postfix/smtpd[2525]: master_notify: status 1 my configuration is sasl2/smtp.conf : pwcheck_method: saslauthd mech_list: PLAIN LOGIN CRAM_MD5 DIGEST_MD5 log_level: 6 smb.conf: [global] workgroup = Biologie2 netbios name = bert server string = bert security = DOMAIN log file = /var/log/samba/log.%m max log size = 50 load printers = No os level = 20 interfaces = dc0 bind interfaces only = yes winbind uid = 10000-20000 winbind cache time = 10 templa...

...xec/dovecot/dovecot-auth > #auth_process_size = 256 > auth_user = root > #auth_chroot = > #auth_count = 1 > #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ > #auth_anonymous_username = anonymous > auth_verbose = yes > > #auth = digest_md5 > #auth_methods = digest-md5 > #auth_realms = > #auth_userdb = passwd-file /etc/passwd.imap > #auth_passdb = passwd-file /etc/passwd.imap > #auth_user = imapauth > #auth_chroot =

hi there, I?m getting such a headache today, I?ve added myself to three mailing lists trying to figure this out, okay here it goes. I?ve got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix, samba/winbind. I?m running winbind to authenticate against Active Directory, I?ve edited my ?/etc/pam.d/dovecot? pam module so to let my users login with there Active directory password, but

...rbose = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-...

...rbose = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-...

...rbose = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-...

...rbose = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-...

...bose = yes # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-...

...debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain diges...

...uid 5000: Permission denied Aug 8 21:23:47 lex dovecot: child 10315 (imap) returned error 89 which is the problem I discussed above, but is it reasonable for Dovecot to disconnect the IMAP socket and not send an error message to the client? At the end of the dovecot-example.conf is: #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = Is auth_methods an alias for auth_mechanisms? Aside from the insufficient detail in the log, most of the difficulty I encounte...

...debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest...

...bose = yes # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md...