Re: Kolab User Passwords

Thomas Reitelbach <[email protected]> Sat, 28 Dec 2024 12:21:11 +0100
Newsgroups gmane.comp.kde.devel.kroupware
Message-ID <CA62129D-E366-4415-823A-B5B70673B624__4217.18694721989$1735384922$gmane$org@erdfunkstelle.de>
--===============1627753234910718310==
Content-Type: multipart/alternative;
 boundary=Apple-Mail-537B6FB6-6A46-437D-B68F-ACE15952CB94
Content-Transfer-Encoding: 7bit


--Apple-Mail-537B6FB6-6A46-437D-B68F-ACE15952CB94
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Tha=
nk you very much for your help.</div><div dir=3D"ltr">I believe that with so=
me System Update the default hash method has changed Without My knowledge.&n=
bsp;</div><div dir=3D"ltr">I will tryto alter the Password The Manual way wi=
th ldappasswd and see What Happens.&nbsp;</div><div dir=3D"ltr"><br></div><d=
iv dir=3D"ltr">Cheers</div><div dir=3D"ltr">Thomas</div><div dir=3D"ltr"><br=
><blockquote type=3D"cite">Am 28.12.2024 um 10:00 schrieb Mihai Badici &lt;m=
[email protected]&gt;:<br><br></blockquote></div><blockquote type=3D"cite"><div=
 dir=3D"ltr">=EF=BB=BF

 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8"=
>
 =20
 =20
    <p>But the problem is the authentication should not be dependent on
      hash type. Authentication is binding the ldap server with user and
      password. If all the utilities ( server and client tools) are
      compatible the authentication should work with any supported hash
      type.<br>
    </p>
    <p>So I guess the problem is when you create a new user ( with kolab
      webadmin I assume) the password is hashed outside the ldap tools
      and inserted as text. I don't use kolab webadmin but I suspect if
      the ldap server is not supporting ssha512 you can change the hash
      algoritm either from config file or directly in the code. <br>
    </p>
    <p>To be more specific: you can change an user password in ldap
      using ldappasswd&nbsp; (from openldap-client) :</p>
    <p><span style=3D"font-family:monospace"><span style=3D"color:#000000;ba=
ckground-color:#ffffff;">ldappasswd -D
          cn=3DManager,dc=3D****** -x -w $rootpass -S "$DN"</span></span></p=
>
    <p>This will use the default hashing in ldap server<span style=3D"font-f=
amily:monospace">.</span></p>
    <p>But you can also use ldapmodify and change the password as a text
      - hashed with any algorithm you choose. If you use that way - and
      for some legitimate reasons I think&nbsp; is the way kolab webadmin is=

      acting - the hash can be or can't be supported. So probably you
      can upgrade ldap server or change the hash algorithm. Also you can
      try to change the password from console as in my example to
      validate my assumption.</p>
    <p>Mihai<span style=3D"font-family:monospace"><br>
      </span></p>
    <p><br>
    </p>
    <p><br>
    </p>
    <div class=3D"moz-cite-prefix">On 12/28/24 01:30, Valentin Laskov
      wrote:<br>
    </div>
    <blockquote type=3D"cite" cite=3D"mid:2697dd36-099a-47ee-bdf7-284093ee35=
[email protected]">Hello,
      <br>
      <br>
      brute force method:
      <br>
      <br>
      1. Make an archive using this method:
      <br>
      <br>
<a class=3D"moz-txt-link-freetext" href=3D"http://web.archive.org/web/202405=
24220349/https://docs.kolab.org/administrator-guide/backup-and-restore.html"=
>http://web.archive.org/web/20240524220349/https://docs.kolab.org/administra=
tor-guide/backup-and-restore.html</a>
      <br>
      <br>
      You will get text files in which the password will look like this:
      <br>
      <br>
      userPassword::
      e1NTSEE1MTJ9MTRGcXZpbE5ScU1mdGNGMFhyYkFZdy9tUkNQcGp5bHZmQ09VTFp
      <br>
&nbsp;kcWJwQ2FXY2ZtN2Y0NWptZnJsRnVSeVpLOVk1eHJ4U25wRTA1WFNQajhYYk0vQnR4dzUrN=
05rMlVz
      <br>
      <br>
      2. Copy and paste a password from another user whose password you
      know to a user whose password doesn't work. Don't tell any user
      about this! :)
      <br>
      <br>
      3. Restore the backup using the description above. It is probably
      possible to improvise to perform a partial restore.
      <br>
      <br>
      4. Cheers and Happy New Year! :)
      <br>
      <br>
      Valentin Laskov
      <br>
      <br>
      =D0=9D=D0=B0 25.12.24 =D0=B3. =D0=B2 14:40 =D1=87., Reitelbach, Thomas=
 =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0:
      <br>
      <blockquote type=3D"cite">Hello list,
        <br>
        <br>
        I'm running Kolab 16 on CentOS 7 with multi domain support (4
        Domains) for some years now.
        <br>
        <br>
        Today I added a new Kolab User and set the password. But the new
        user can't login with roundcube ("Login failed" says
        roundcubemail). And the logs also say failed login.
        <br>
        <br>
        Old users can still login as usual with their password.
        <br>
        <br>
        After some investigation I found that "kolab user-info
        user@domain" shows a "userpassword:" with
        <br>
        <br>
        u'{SSHA512}................'
        <br>
        <br>
        and old users are encrypted like this:
        <br>
        u'{SSHA}................'
        <br>
        <br>
        I guess that with some system update something in the underlying
        system has changed and new passwords are beeing stored as SHA512
        now, which makes roundcube or ldap fail to check the password.
        <br>
        <br>
        Has anyone help for me? Can I setup how roundcube webadmin will
        encode the password in LDAP?
        <br>
        Can I manually set the password in LDAP?
        <br>
        I'm not familiar with LDAP queries and need help with that.
        <br>
        <br>
        Have a nice Christmas :)
        <br>
        <br>
        Thomas
        <br>
        _______________________________________________
        <br>
        users mailing list
        <br>
        <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]=
ab.org">[email protected]</a>
        <br>
        <a class=3D"moz-txt-link-freetext" href=3D"https://lists.kolab.org/m=
ailman/listinfo/users">https://lists.kolab.org/mailman/listinfo/users</a>
        <br>
      </blockquote>
      _______________________________________________
      <br>
      users mailing list
      <br>
      <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]=
.org">[email protected]</a>
      <br>
      <a class=3D"moz-txt-link-freetext" href=3D"https://lists.kolab.org/mai=
lman/listinfo/users">https://lists.kolab.org/mailman/listinfo/users</a>
      <br>
    </blockquote>
 =20

<span>_______________________________________________</span><br><span>users m=
ailing list</span><br><span>[email protected]</span><br><span>https://li=
sts.kolab.org/mailman/listinfo/users</span><br></div></blockquote></body></h=
tml>=

--Apple-Mail-537B6FB6-6A46-437D-B68F-ACE15952CB94--

--===============1627753234910718310==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
users mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/users

--===============1627753234910718310==--