search for: argon2id

I'm using dovecot version 2.3.2.1 (0719df592) and trying to use the ARGON2ID crypt scheme for authentication using the passdb passwd-file driver. My passdb config is very simple: ??? passdb { ????? driver = passwd-file ????? args = username_format=%u <path-to-file-here> ??? } If I generate a password this way: ??? doveadm pw -s ARGON2ID -p 'This is a test&...

Hello, I'm using dovecot 2.3.4.1 on a Debian buster system. with Argon2ID password scheme, it's only possible to configure the parameters used for it via the generic -r option to "doveadm pw". A higher -r will increase time and memory comsumption. But on my dual core VM it always uses p=1. So it seems the needed threads can only be changed on compile time?...

...ocess runs out of memory and there is a bug in libsodium which causes it to crash in this scenario. The fix is to do service auth { ? vsz_limit = 0 # or 2G at least } Aki On 26.09.2018 09:12, Keith Amidon wrote: > I'm using dovecot version 2.3.2.1 (0719df592) and trying to use the > ARGON2ID crypt scheme for authentication using the passdb passwd-file > driver. My passdb config is very simple: > > ??? passdb { > ????? driver = passwd-file > ????? args = username_format=%u <path-to-file-here> > ??? } > > If I generate a password this way: > > ??? dove...

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 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CRYPT CRYPT SSHA MD5-CRYPT SKEY PLAIN-MD4...

> On 16/08/2020 09:38 Felix Zielcke <fzielcke at z-51.de> wrote: > > > Hello, > > I'm using dovecot 2.3.4.1 on a Debian buster system. > > with Argon2ID password scheme, it's only possible to configure the > parameters used for it via the generic -r option to "doveadm pw". > > A higher -r will increase time and memory comsumption. > But on my dual core VM it always uses p=1. > So it seems the needed threads can only be...

...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 (uid=214): auth-worker<1>: sql(jlbrown at bordo.com.au,::1,<bRgbkDP2udEBAAAAAAAAAAAAAAAAAAB>): Unknown scheme ARGON2ID > > ./configure --with-ssl=openssl --with-mysql > > Was what I used to compile. > > Using OpenSSL 3.0.8. New server is running macOS 13.2.1 Ventura. > > (Have also installed libsodium 1.0.18_1) > > Any help would be most appreciated. > > thanks, > >...

On my current mail server I was able to upgrade everyone?s password scheme to ARGON2ID with no issues, I just had to have: service auth { vsz_limit = 0 } This was an older version of macOS than the new server I?m trying to migrate to. The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate: Feb 21 21:51:03 master: Info: D...

...1 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 (uid=214): auth-worker<1>: sql(jlbrown at bordo.com.au,::1,<bRgbkDP2udEBAAAAAAAAAAAAAAAAAAB>): Unknown scheme ARGON2ID > > > > ./configure --with-ssl=openssl --with-mysql > > > > Was what I used to compile. > > > > Using OpenSSL 3.0.8. New server is running macOS 13.2.1 Ventura. > > > > (Have also installed libsodium 1.0.18_1) > > > > Any help would b...

> 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

...ovecot/users file isn't pam ??? I don't need pam if if I'm using /etc/dovecot/users ?? Or am I understanding you wrong? > > you have passdb block using pam. it is involved in the lookup process.? > > --- > Aki Tuomi > doveconf -n passdb userdb passdb { ? args = scheme=ARGON2ID username_format=%u /etc/dovecot/users ? auth_verbose = yes ? driver = passwd-file } userdb { ? args = scheme=ARGON2ID username_format=%u /etc/dovecot/users ? auth_verbose = yes ? driver = passwd-file }

...ovecot.org on behalf of jerry at seibercom.net> wrote: > > 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 SSHA512 BLF-CRYPT...

...doveadm pw -l > > > SHA1 SSHA512 SCRAM-SHA-256 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA DES-CRYPT CRYPT SSHA MD5-CRYPT PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 CLEAR CLEARTEXT SSHA256 MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SMD5 DIGEST-MD5 LDAP-MD5 > > > > > > How do I get ARGON2I, ARGON2ID in that list? > > > > > > Has anybody got Dovecot to work on recent macOS with these password schemes? Any hints? > > > > > > Thanks, James. > > > > You need to use --with-sodium when building. > > > > Aki > > Thanks Aki, that w...

> On 22 Feb 2023, at 5:33 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> >> Thanks Aki, that was helpful. When I add that I get: >> >> checking for LIBSODIUM... no >> configure: error: Can't build with libsodium: not found >> >> So I have to tell it where libsodium is. >> >> Tried: >> >>

> On 22/02/2023 08:41 EET James Brown <jlbrown at bordo.com.au> wrote: > > > > On 22 Feb 2023, at 5:33 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > Thanks Aki, that was helpful. When I add that I get: > > > > > > checking for LIBSODIUM... no > > > configure: error: Can't build with libsodium: not

...ot; <dovecot-bounces at dovecot.org on behalf of jerry at seibercom.net> wrote: 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 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CR...

...20 imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no dsync_features = empty-header-workaround dsync_commit_msgs_interval = 100 # default in v2.2.30+ dsync_hashed_headers = Date Message-ID and grep users.conf /etc/dovecot/conf.d/* /etc/dovecot/conf.d/10-auth.conf: args = scheme=ARGON2ID /etc/dovecot/sec/users.conf _USER="testuser at example.net" _PASS="my!secret" _PASS_ENC=$( doveadm pw -s ARGON2ID -p ${_PASS} ) echo "${_USER}:${_PASS_ENC}::::" >> /etc/dovecot/sec/users.conf grep testuser at example.net /etc/dovecot/sec/users.conf testu...

...;t need pam if if I'm using /etc/dovecot/users ?? Or am I understanding you wrong? > > > > you have passdb block using pam. it is involved in the lookup process.? > > > > --- > > Aki Tuomi > > > doveconf -n passdb userdb > passdb { > ? args = scheme=ARGON2ID username_format=%u /etc/dovecot/users > ? auth_verbose = yes > ? driver = passwd-file > } > userdb { > ? args = scheme=ARGON2ID username_format=%u /etc/dovecot/users > ? auth_verbose = yes > ? driver = passwd-file > } Looks OK now. PAM is quite often the culprit as it's...

...th the distro's rpms and not take on building and </div> <div> >> maintaining myself. </div> <div> > </div> <blockquote type="cite"> <div> And for the record, the hash names are ARGON2I and ARGON2ID (see doveadm </div> <div> pw -l ) </div> </blockquote> <blockquote type="cite"> <div> With dovecot from the dovecot.org < <a href="http://dovecot.org" rel="noopener" target="_b...

Hello everyone. I'm close to completing my first build of a mail server - Postfix, Dovecot, Postgres (I know, sounds like overkill), Rspamd with Redis and Unbound (please infer a mega lack of experience disclaimer). The model is standalone internet with remoted sasl-authenticated clients. Throughout the process I've been having consistent problems with user password authentication.

On Thursday, April 11, 2019 2:02 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > PAM is trying to lookup user at domain while you probably only have user. PAM driver does not yet support username_format.? > > Aki But /etc/dovecot/users file isn't pam ??? I don't need pam if if I'm using /etc/dovecot/users ?? Or am I understanding you wrong?