On Sun, 3 Mar 2019 at 01:37, Ludovic Marcotte wrote:
> On 2019-03-02 11:31 a.m., Odhiambo Washington (odhia...@gmail.com) wrote:
>
> > Is this something that can be avoided?
> By setting prependPasswordScheme = NO.
>
>
Thank you.
I realize now I MUST take time to go through the documentation (te
On 2019-03-02 11:31 a.m., Odhiambo Washington (odhia...@gmail.com) wrote:
Is this something that can be avoided?
By setting prependPasswordScheme = NO.
--
Ludovic Marcotte
lmarco...@inverse.ca :: +1.514.755.3630 :: https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), P
I am able to change passwords, right, but I see that the password
encryption scheme prepended to the encrypted password in the DB.
Is this something that can be avoided?
And why is digest-md5 not among the supported encryption algorithms?
I don't see it listed in the Docu under "Possible values" w
Hi,
I have generated a plain text MD5. For me is a strange thing that I can
login with the md5 string. For example in the settings are /md5/ for
userPasswordAlgorithm, in the database for tes.user the password is
1f3870be274f6c49b3e31a0c6728957f, I can login with this string but with
the valu
Hi,
could you give us more details on your system, like which version of SOGo
you're running, the kind of MD5 (plain or crypt-MD5)... ?
Can you see the queries SOGo is issuing to the SQL server, for example in a
query log?
Without these details, it's difficult to give you any hints.
Regards,
Hi list!
I have a problem configuring the sogo to use md5 for user passwords.
Before I have made the change of userPasswordAlgorithm to md5 the user
could log in to the system.
After the change from /none/ to /md5 /the user couldn't login with the
value of md5 string.
This is a part from my co
