similar to: Support for multiple passwords?

Am 2015-03-18 20:46, schrieb Reindl Harald: > Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >> Hi! >> Currently, the passwords are stored in plaintext for my dovecot, as I >> am >> still using cram-md5 AND digest-md5. >> I have still to offer that, as I have some deprecated clients, >> therefore, I am unable to hash at least those passwords for that

Quoting Reindl Harald <h.reindl at thelounge.net>: > Am 18.03.2015 um 20:56 schrieb Conrad Kostecki: >> Am 2015-03-18 20:46, schrieb Reindl Harald: >>> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >>>> Hi! >>>> Currently, the passwords are stored in plaintext for my dovecot, as I >>>> am >>>> still using cram-md5 AND

Am 18.03.2015 um 20:56 schrieb Conrad Kostecki: > Am 2015-03-18 20:46, schrieb Reindl Harald: >> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >>> Hi! >>> Currently, the passwords are stored in plaintext for my dovecot, as I am >>> still using cram-md5 AND digest-md5. >>> I have still to offer that, as I have some deprecated clients, >>>

Hello List, The only passdb block in /pfx/etc/dovecot/dovecot.conf is: passdb ldap { args = /pfx/etc/dovecot/dovecot-ldap.conf } In /pfx/etc/dovecot/dovecot-ldap.conf: auth_bind = no dn = cn=mymgr,dc=host,dc=tld dnpass = ******** default_pass_scheme = LDAP-MD5 In /pfx/etc/openldap/slapd.conf: password-hash {MD5} If I try: $ /pfx/bin/ldapsearch <...> \ | grep

Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: > Hi! > Currently, the passwords are stored in plaintext for my dovecot, as I am > still using cram-md5 AND digest-md5. > I have still to offer that, as I have some deprecated clients, > therefore, I am unable to hash at least those passwords for that accounts. > > I've found on the Wiki: >> In future it's possible

Am 2015-03-18 21:10, schrieb Rick Romero: > Quoting Reindl Harald <h.reindl at thelounge.net>: > >> Am 18.03.2015 um 20:56 schrieb Conrad Kostecki: >>> Am 2015-03-18 20:46, schrieb Reindl Harald: >>>> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >>>>> Hi! >>>>> Currently, the passwords are stored in plaintext for my dovecot,

On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: > >> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >> > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and >> perhaps a few others but this should be resolved in the master branch. >> > I just committed my fix this morning so there's no -pre

On Sun, Feb 2, 2014 at 12:34 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: >> On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >>> >>>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>>> > Known

On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >> >>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>> > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and >>> perhaps a few others but this should

I config postfix+mysql+dovecot for SASL SMTP autentication. It works if set: default_pass_scheme = PLAIN and store plain-text password in mysql I'm change default_pass_scheme = PLAIN with default_pass_scheme = PLAIN-MD5 an store password in mysql with md5('passwd') and dovecotpw -s PLAIN-MD5 -p test {PLAIN-MD5} and md5("test") = 098f6bcd4621d373cade4e832627b4f6 but

On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and perhaps a few others but this should be resolved in the master branch. > I just committed my fix this morning so there's no -pre release yet. Is that really fixed in git? I've checkout syslinux about one hour ago from git. I ran a make all

> Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5 The web is flooded with plain text passwords and hashed passwords harvested from hacked servers. Dovecot stores passwords with the same scheme used for client authentication. Therefore, we use crammd5/hmac-md5. It does not look like much, but is better than plaintext. As md5 is about to go, and I have no intention to

After upgrading my dovecot installation about a month ago, I have started seeing "Requested CRAM-MD5 scheme, but we have only MD5-CRYPT" message from dovecot in my logs. Any help in finding and correcting the cause will be greatly appreciated. --Richard

Hi there, I am trying to setup a bootable PXELinux (Using 6.02) over UEFI. Currently, I am using DNSMasq for this. PXE with BIOS works perfectly fine for me. As I don't have any UEFI devices here, I am using VMware Workstation 10.0.1 for testing. My DNSMasq setup has been extended, to load also UEFI: dhcp-boot=pxelinux.0 dhcp-match=set:efi-ia32,option:client-arch,6

Hi Folks, I'm fairly new to linux so this message may reflect that. dovecot info (running on CentOS 5.0): protocols: pop3s listen: ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_executable:

Is it possible to save user passwords as clear text through dovecot? I am currently using MD5 passwords and I allow only "plain and login? mechanisms but I want to switch my database to clear text as this will give me the ability to use more mechanisms such as CRAM-MD5. Is this possible? Thank you

hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future, will it still work? or must they always from this point on use encrypted passwords? Thanks. -- Thanks,

I wasn't able to get DIGEST-MD5 authentication working with passwords stored as plaintext until I tweaked password_generate() to make it not use the domain portion of user at domain.com as the realm. Both evolution and kmail send the email address as the username with no realm; when dovecot tries to convert the username to user + realm, the hash is different and so DIGEST-MD5

When using proxy_maybe CRAM-MD5 authentication fails when the connection is proxied. Is this expected behavior? Is proxy_maybe too simplified for this case? We're using SQL so I could rewrite the query with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS

On 19.6.2019 7.48, Alexander Dalloz via dovecot wrote: > Am 19.06.2019 um 00:04 schrieb Jorge Bastos via dovecot: >> Howdy, >> >> I'm using dovecot and mysql users, and i'm creating the password with: >> >> ENCRYPT('some-passwd',CONCAT('$6$', SUBSTRING(SHA(RAND()), -16))) >> >> So far so good, everything's fine. >>