Sorry not truncated:
{SHA512-CRYPT}$6$wEn1UFuiMzl9OSjd$Vh/PZ95WDID1GwI02QWAQNNfY5.Rk9zcSetYTgRfo4SPKf8qzMXsruvvS8uaSUidlvwDTLLSr3cVsQx2e6cu2/
------------
You have a good day now, en mag jou môre ook so wees,
Carl A Jeptha
On 2016-04-30 14:58, Patrick Domack wrote:
This looks good, except it is truncated, it should be something like
95chars long, Is your hash column set to 128 or up around there or
larger?
Quoting Carl A Jeptha <cajep...@gmail.com>:
Sorry for double reply, but this what a password looks like in the
"hashed" password column:
{SHA512-CRYPT}$6$wEn1UFuiMzl9OSjd$Vh/PZ95WDID1GwI2
------------
You have a good day now, en mag jou môre ook so wees,
On 2016-04-30 01:14, Gedalya wrote:
That's not SHA512-CRYPT. That's just a simple sha512 of the
password, without salt.
A SHA512-CRYPT password will be generated with:
printf "1234\n1234" | doveadm pw -s SHA512-CRYPT
or:
doveadm pw -s SHA512-CRYPT -p 1234
or:
mkpasswd -m sha-512 1234
(without the "{SHA512-CRYPT}" prefix)
What exactly is the difficulty you are having with converting the
passwords?
What database engine are you using?
On 04/29/2016 03:20 PM, Bill Shirley wrote:
Looks like an SQL update would do this:
UPDATE `users`
SET `passwd_SHA512` = SHA2(`passwd_clear`, 512);
Bill
On 4/29/2016 9:07 AM, Carl A Jeptha wrote:
converting the passwords in the database from clear/plain text to
SHA512-CRYPT
