similar to: Samba LDAP - bug in ldapsync.pl

I've got a Samba 2.2.7a domain with an LDAP backend. It's been working for nearly 3 months now without much bother. By the way: Great work and thanks for all of the effort! I have been missing one minor thing from the setup since I moved away from NT 4: Password Expiration. In the past I have posted questions about this on the list and I've gotten two answers: "Wait for

Hi, Why you sp?cifie : smb passwd file = /etc/samba/smbpasswd pam password change = Yes If you use LDAP ? It's the interaction between LDAP and these parameter which cause the problem. ----------------------------------- St?phane PURNELLE stephane.purnelle@corman.be Service Informatique Corman S.A. Tel : 00 32 087/342467

I am trying to get 'net password ...' to work from an OS/2 client to a Samba 3.1.15 server. However, I get an Invalid Password error whenever I run net password. I am certain that I am providing the correct password. With DEBUG_PASSWORD on in the build and tracing set to 100 I ran 'net view \\server' which authenticates correctly and I ran 'net password user oldpass

Hi... I wonder if someone can shed some light onto a password changing problem I'm having with 2.0.6. I have a script that is launched using the 'unix sync' procedure which all worked fine in 2.0.5a which using a script like this. #!/bin/sh echo "Enter old password:" read $OLDPASS ... ... I've only listed the first two lines as this is where it's getting stuck.

When I am setup external passwd change script (syncldap) for sync my smb pass and unix pass, and change smb password on my windows client client, him return error, but password change is successful! It's log from samba for my windows client machine: [2004/08/04 11:46:52, 3] smbd/chgpasswd.c:chat_with_program(424) chat_with_program: Dochild for user g-marchenko (uid=0,gid=0) (as_root =

Hello, I''m having a weird problem in my user model. For the change_password method I have the following: def change_password(oldpass, newpass, confirmation) oldpass = self.class.myhash(oldpass) reload passhash = self.password self.password = newpass self.password_confirmation = confirmation if valid? and oldpass == passhash save! else # valid?

Hi all, I have found the smbldap-tools provided in the samba 3 tarball to have a few glitches with the samba 3 schema. I have made my changes and 'diffed' them with the source. root@localhost # pwd /usr/local/samba/sbin root@localhost # for i in *.p*; do echo $i; diff $i /usr/local/src/samba-3.0.0rc4/examples/LDAP/smbldap-tools/$i; done smbldap-groupadd.pl smbldap-groupdel.pl

Hello list I have a problem that i am confronting for long time and i dont get a result. We use samba 3.0.24 (also tried other versions) with openldap and the smbldap-tools on Suse Linux SLES9. We use openldap for user authentikation for samba (objectClass: sambaSamAccount) and other application like email, apache, squid (objectClass: shadowAccount and objectClass: posixAccount). My scope

Hi! Does this sound familiar, before I try to look deeper into it? [2005/02/13 20:10:16, 0] /usr/ports/net/samba/w-samba-3.0.11/samba-3.0.11/source/libsmb/smbencrypt.c:decode_pw_buffer(539) decode_pw_buffer: incorrect password length (1251354155).

Has anyone got unix password sync for samba3.0.x running successfully on SLES8 server? Do I need the SLES service packs? Is there an interaction with PAM that I need to be aware of? I've compiled the full developer build of samba from 3.0.4-4 source. Compile was successful. I'm running tdbsam as password backend. I've troubleshooted quit a bit using google, docs, etc. as

Hello, I am currently migrating from OpenLDAP to Samba 4 PDC, and I have a webpage (PHP/Apache) available for users so that they can change their password on the existing LDAP server. I attempted to adjust that script to change the password on the Samba 4 AD controller, but I get a "cannot connect" error to LDAP. The web server the password script is running on is not on the same

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, I have aproblem with the smbldap-tools...when I try to change the passwd fron a user in win...I get the error "....", and I know that the script of smbldap-tools fails when try to execute the next line: # non-root user if (!defined($oldpass)) { # prompt for current password system "stty -echo"; print "(current)

Hi, I just upgraded my server to support Windows 7 and so installed Samba 3.5.4 from 3.2.5. OS is Debian Lenny. Now my Windows XP clients cannot join the Domain. When joining the Domain, I get a wrong password error on Windows. In my samba logs it shows the following: [2010/08/03 12:10:19.681501, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint

On Tue, 03 Apr 2018 23:34:13 -0400 Mark Foley via samba <samba at lists.samba.org> wrote: > On Sat, 31 Mar 2018 17:04:22 +0100 Rowland Penny <rpenny at samba.org> > wrote: > > > > On Sat, 31 Mar 2018 11:42:07 -0400 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > On Sat, 31 Mar 2018 12:25:14 +0100 Rowland Penny > >

Hi list I'm have a samba (2:3.5.4~dfsg-1ubuntu8.4) domain with LDAP backend and I'm getting the following error when I try to change my domain password via Windows XP: "The User name or old password is incorrect. Letters in passwords must be typed using the correct case". The password is typed correctly and it does get changed in LDAP though. This snippet from the log may

Hello! SuSE Linux 10.0 Samba 3.0.20b OpenLDAP backend IDEALX scripts v0.9.2 Windows XP SP2 client Everything seems to be working except when changing your password from the Windows client (CTRL-ALT-DEL and "Change password"). When I try to change the password I get the following error message. "The User name or old password is incorrect. Letters in passwords must be typed

Hello, I have a following test environment: 1) Samba PDC + OpenLDAP Slave (192.168.1.2) 2) OpenLDAP Master (192.168.1.1). Whatever is changed/added on the Master, it gets replicated to Slave. Now, when a user is logged in, and tries to change the password - he/she must supply the old password, and twice new one (normal behaviour). After pressing OK the user is said that the password

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7. A security hole has been discovered in versions 2.2.2 through 2.2.6 of Samba that could potentially allow an attacker to gain root access on the target machine. The word "potentially" is used because there is no known exploit of this bug, and the Samba Team has not been able

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7. A security hole has been discovered in versions 2.2.2 through 2.2.6 of Samba that could potentially allow an attacker to gain root access on the target machine. The word "potentially" is used because there is no known exploit of this bug, and the Samba Team has not been able

I'm switching from OpenLDAP to the newly released Fedora Directory Server (formely known as the Netscape Directory Server) as a LDAP backend for my Samba domain. I'm now faced with a problem regarding how Fedora DS handles the userPassword field. Unlike OpenLDAP it encodes it in base64 so instead of reading userPassword: {SSHA}0lP+r3Z1NVan7Caf4CG9oSgnTbQRrv/p it reads: userPassword::