Re: [Samba] smbldap-passwd fails

2007-11-10 Thread Jerome Tournier
Hello which smbldap-tools'vesion ? What do you have defined for hash_encrypt parameter in smbldap.conf ? -- Jerome On 11/9/07, Bernhard D Rohrer [EMAIL PROTECTED] wrote: Hi folks I am getting this error: [EMAIL PROTECTED]:/home/admin# smbldap-passwd testuser Changing UNIX and samba

[Samba] smbldap-passwd fails

2007-11-09 Thread Bernhard D Rohrer
Hi folks I am getting this error: [EMAIL PROTECTED]:/home/admin# smbldap-passwd testuser Changing UNIX and samba passwords for testuser New password: Retype new password: I cannot generate the proper hash! uncle google was rather quiet on the subject :( what do you need config file wise?

RE: [Samba] smbldap-passwd

2007-03-23 Thread Adrian Sender
May be worth checking your slapd.conf ACL's. Adrian Sender -Original Message- From: Chechu [mailto:[EMAIL PROTECTED] Sent: Friday, 23 March 2007 8:12 AM To: samba Subject: [Samba] smbldap-passwd -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, I'm trying to make works this script

[Samba] smbldap-passwd

2007-03-22 Thread Chechu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, I'm trying to make works this script...from linux it works right with all users...but in win...it fails when try to do this line of script: chomp($pass=STDIN); In win i got this error: No tiene permiso para cambiar su contraseƱa you dont have

[Samba] smbldap-passwd

2007-03-22 Thread Chechu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, I'm trying to make works this script...from linux it works right with all users...but in win...it fails when try to do this line of script: chomp($pass=STDIN); In win i got this error: No tiene permiso para cambiar su contraseƱa you dont have

[Samba] smbldap-passwd and uppercased schemes

2006-06-26 Thread Logan Shaw
Hey everyone, I'm looking at the IDEALX smbldap-passwd script (the version which comes with samba 3.0.22, in the examples directory), and it seems to want to set the password scheme to an uppercase string, i.e.: {CRYPT}foobarfoobar {MD5}barfoobarfoo However, looking at RFC 2307 (