On Sun, 16 Jul 2017 14:20:27 -0700 (PDT)
Joseph Tam wrote:
> Using user@domain as your ID solved your problem, and this side issue
> of which hash scheme you're using is probably irrelevant.
>
> You misunderstand what {SHA512-CRYPT} does compared with {SHA512}.
> It is normal to get a different
Lev wrote:
Yes, that was a bit odd. Same password, different hash. Even with
verify tool, there was mismatch. So I decided to go for SHA512,
without encryption.
Using user@domain as your ID solved your problem, and this side issue
of which hash scheme you're using is probably irrelevant.
On Fri, 14 Jul 2017 13:46:01 -0700 (PDT)
Joseph Tam wrote:
> > I continuously get user authentication errors. I suspect that the
> > problem is with a password hashing. I used
> >
> > # doveadm pw -s SHA512-CRYPT
> > Enter new password:
> > Retype new password:
> > {SHA512-CRYPT}$6$1cCNWIMCTpuqme
Levente Kovacs writes:
I continuously get user authentication errors. I suspect that the problem is
with a password hashing. I used
# doveadm pw -s SHA512-CRYPT
Enter new password:
Retype new password:
{SHA512-CRYPT}$6$1cCNWIMCTpuqmexO$cCq7nDEga1xza3967nZ.BFZaGWNoYwjnNfSCvZE/jGzYAY1hLWE1iHR1KYa
