Henrique

From: "Henrique" <>
Newsgroups: linux.samba
Subject: [Samba] smbldaptools with SSHA
Date: Fri, 02 Jul 2004 05:20:06 +0200
Message-ID: <2dmKO-5Fz->
X-Original-To: "Samba Samba" <>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0005_01C45FC9.F6315570"
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Content-Filtered-By: Mailman/MimeDel 2.1.4
Reply-To: Henrique <>
List-ID: General questions regarding Samba <samba.lists.samba.org>
List-Archive: <http://lists.samba.org/archive/samba>
Sender:
Approved:
Lines: 77
Organization: linux.* mail to news gateway
X-Original-Date: Fri, 2 Jul 2004 00:17:29 -0300
X-Original-Message-ID: <000901c45fe3$1def3f50$05050180@henrique>
X-Original-Sender: samba-bounces+linux.samba=
Path: artemis.britishexpats.com!wn14feed!worldnet.att.ne t!207.115.63.142!prodigy.com!news.glorb.com!news.n ewsland.it!area.cu.mi.it!bofh.it!news.nic.it!robom od
Xref: artemis.britishexpats.com linux.samba:54903

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C45FC9.F6315570
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello All!
im trying to get smbldap-tools to work with SSHA hash, but this not =
working..
if i use clear text this work fine, all .confs and log is attached..

Some idea?

------=_NextPart_000_0005_01C45FC9.F6315570
Content-Type: text/plain;
name="smbldap-populate-output.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="smbldap-populate-output.txt"

-bash-2.05b# smbldap-populate
Using builtin directory structure
Use of uninitialized value in string ne at =
/usr/local/sbin/smbldap-populate line 107.
Use of uninitialized value in concatenation (.) or string at =
/usr/local/sbin/smbldap-populate line 111.
adding new entry: dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 2.
adding new entry: ou=3Dusuarios,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 3.
adding new entry: ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 4.
adding new entry: ou=3Dhosts,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 5.
adding new entry: uid=3DAdministrator,ou=3Dusuarios,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 6.
adding new entry: uid=3Dnobody,ou=3Dusuarios,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 7.
adding new entry: cn=3DDomain Admins,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 8.
adding new entry: cn=3DDomain Users,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 9.
adding new entry: cn=3DDomain Guests,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 16.
adding new entry: cn=3DPrint Operators,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 17.
adding new entry: cn=3DBackup Operators,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 18.
adding new entry: cn=3DReplicator,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 19.
adding new entry: cn=3DDomain Computers,ou=3Dgrupos,dc=3Dmoove
failed to add entry: modifications require authentication at =
/usr/local/sbin/smbldap-populate line 344, <GEN1> line 19.

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

Helge

Finally I found the bug!!!

The tools want to have the password in eye-readable form, not in the encrypted form as slappasswd displays it.

In other words:

you may configure the rootpw entry in slap.conf and ldap.conf with something like this:

{SSHA}dL7lumc9mW2V4461jtEPyLRiiQc7uKKu

However in the smbldap-bind.conf you simply have to write "test" (in this example).

There is another error coming up when trying to populate the entries, but this can be resolved by adding "objectclass = namedObject" to the sections in smbldap-populate where the various objects are defined.

The question is if it wouldn't be easier to generate the configuration the old-fashioned way using ldapadd and a file....