similar to: Moving to new password scheme

> On Jan 25, 2017, at 1:09 AM, Alessio Cecchi <alessio at skye.it> wrote: > > Il 24/01/2017 23:29, @lbutlr ha scritto: >> dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably SSHA256-CRYPT, but I want to do this seamlessly without the users having to jump through any hoops. >>

> On Jan 25, 2017, at 2:46 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 25 Jan 2017, @lbutlr wrote: >>> On Jan 25, 2017, at 1:09 AM, Alessio Cecchi <alessio at skye.it> wrote: >>> >>> Il 24/01/2017 23:29, @lbutlr ha scritto: >>>> dovecot is setup

Il 24/01/2017 23:29, @lbutlr ha scritto: > dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably SSHA256-CRYPT, but I want to do this seamlessly without the users having to jump through any hoops. > > The users are in mySQL (managed via postfixadmin) and the mailbox record simply stores the hash in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 25 Jan 2017, @lbutlr wrote: >> On Jan 25, 2017, at 2:46 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Wed, 25 Jan 2017, @lbutlr wrote: >>>> On Jan 25, 2017, at 1:09 AM, Alessio Cecchi <alessio at skye.it>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 25 Jan 2017, @lbutlr wrote: >> On Jan 25, 2017, at 1:09 AM, Alessio Cecchi <alessio at skye.it> wrote: >> >> Il 24/01/2017 23:29, @lbutlr ha scritto: >>> dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably

I have trying to find how to set the dovecot-sql.conf for using SHA256/512.? I am going to start clean with the stronger format, not migrate from the old MD5.? It seems all I need is: driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=$Postfix_Database_Password default_pass_scheme = SHAxxx-CRYPT # following should all be on one line. password_query =

I'm getting a very strange error and I'm completely mystified by it. Thank you so much for taking a look! I recently migrated some users from another dovecot server to my own, and the previous admin had the passwords in their database using the SSHA256 scheme in HEX format. All the password hashes are in my database (MySQL) with a {SSHA256.HEX} prefix, and I thought at first that they

On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote: > > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate: > > Feb 21 21:51:03 master: Info: Dovecot v2.3.20 (80a5ac675d) starting up for imap, pop3 (core dumps disabled) > Feb 21 21:51:33 auth-worker(11701): Error: conn unix:auth-worker

> On 22/02/2023 07:00 EET James Brown <jlbrown at bordo.com.au> wrote: > > > On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote: > > > > > > > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate: > > > > Feb 21 21:51:03 master: Info: Dovecot v2.3.20

Hi again, I`m a bit confused how to store a SSHA256 password in the database and I can`t find any information in the wiki. Do I have to store the SHA256 hash and the salt separately (what would the password_query be like in this way) or just the final SSHA256 hash? Regards Patrick

> On 22/02/2023 09:10 EET James Brown <jlbrown at bordo.com.au> wrote: > > > On 22 Feb 2023, at 5:53 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > > > > > > > > > > % locate libsodium > > > > > /opt/homebrew/Cellar/libsodium > > > > > /opt/homebrew/Cellar/libsodium/1.0.18_1

on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play nice with "argonid" encryption. In the "10-auth.conf" file, I tried: auth_mechanisms = plain argon2id Upon restarting dovecot, I received an error message when attempting to actually it: auth: FATAL: Unknown authentication mechanism "ARGON2ID" Output from doveadm pw -l doveadm pw -l SHA1

Hi! I noticed these messages in my logs. It seems that the user checked the "encrypted password" in her outlook or something, and wants NTLM auth. I'm storing all the passwords as SSHA256, and when the user tries to auth, this happens: => dovecot.info auth: Info: password(<username>,<user_ip>): Requested NTLM scheme, but we have only SSHA256 auth: Debug:

(I subscribed to a daily digest for this list and can?t figure out how to reply to a reply.) Anyway, Aki Tuomi replied to my feature request saying: > We support in latest 2.2 release > > MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN > CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 > PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY

I am using a FreeBSD 11-2 amd/64 system with dovecot version 2.3.4 installed. I was playing around with different encryption schemes. doveadm pw -l SHA1 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CRYPT CRYPT SSHA MD5-CRYPT SKEY PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 LANMAN SHA512-CRYPT CLEAR CLEARTEXT SSHA256 NTLM MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5

On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote: > > > Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz > <rgm at htt-consult.com>: > >> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote: >>> Am 12.02.2019 um 17:05 schrieb Robert Moskowitz via dovecot: >>>> I have trying to find how to set the dovecot-sql.conf for using

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

converting the passwords in the database from clear/plain text to SHA512-CRYPT ------------ You have a good day now, en mag jou m?re ook so wees, Carl A Jeptha On 2016-04-29 15:02, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 29 Apr 2016, Carl A Jeptha wrote: > >> Good Day, >> I have been following this tutorial without much

Hi, I have a current auth database using mysql with a "password" column in plain text. The config has "default_pass_scheme = PLAIN" specified In preparation for a more adaptable system I changed a password entry from "asdf" to "{PLAIN}asdf", but now auth fails. Works fine if I change it back to just "asdf". (I don't believe it's a