Hello
Am 27.01.22 um 17:37 schrieb David Matthews:
> hi Christian
>
>> Did the password hash algorithm change between devuan 3 and 4? You
>> can check that in your /etc/shadow file.
>
> As I understand, devuan is pretty much debian without systemd? And
> that if you were prepared to do a fair
lling to no
> effect.
>
>>
>> 1. Re: can't authenticate (Christian Mack)
>>
>>
>> --
>>
>> Message: 1
>> Date: Thu, 27 Jan 2022 11:42:22 +0100
>> From: Christian Mack >ch
Hello
> passdb {
> driver = pam
> }
Is user fred defined on your development machine?
Does the password match the one from the production machine?
Kind regards,
Christian Mack
On 26.01.22 21:14, David Matthews wrote:
> My live mail exchanger and development machines have identical dovecot
On 9/26/18 2:42 AM, Aki Tuomi wrote:
The reason it fails is because auth process 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
}
After testing this evening, I can confirm that
The reason it fails is because auth process 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
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
}
If I generate a password this way:
