Forcing Samba to recognize 15 char password

Yaqoob, Mohammad Mohammad.Yaqoob at usi.com
Mon Jun 14 07:12:28 MDT 2010


Thanks for your reply:
I am using samba version: smbd version 3.0.25a.
  
Solaris version 9: SunOS 5.9 Generic_118558-11
I will try the following and let you know.
1: update the samba to the latest version.


Thanks and Regards


-----Original Message-----
From: Andrew Bartlett [mailto:abartlet at samba.org] 
Sent: Monday, June 14, 2010 7:25 AM
To: Yaqoob, Mohammad
Cc: samba-technical at lists.samba.org
Subject: Re: Forcing Samba to recognize 15 char password

On Sun, 2010-06-13 at 21:24 -0400, Yaqoob, Mohammad wrote:
> 
> Hi, Anyone knows how to force samba on Solaris 9 to recognize 15 char
> password from windows client.  I have setup pdbedit as  "min password
> length" to 15, but unfortunately windows drive mapping doesn't work with
> 15 char password and works with first 8 char of the same 15 char
> password.  

So, it seems your unnamed Samba version again suffers from a very nasty
and well known bug in Solaris 9.

The problem is, Solaris will only return the first 8 characters of
getpass().  We have no test to detect this behaviour, but we do have a
configure test that determines if we have been able to compile a
replacement for it.

The problem is, on most other Unix like systems (including Linux), it
does not matter if this configure test passes or fails, as getpass() on
all other systems returns any length password (ie, more than 8 chars).
As such, any failure to compile our replacement may go unnoticed for a
long time.  Similarly, if your particular dev environment does not allow
us to compile a replacement for any reason, we will use the buggy system
one. 

Anyway, I would first suggest you try the latest Samba version (in case
someone fixed it).  Otherwise, you need to investigate why our getpass()
replacement won't compile on your system.

In the long term, if we want to fix this properly, we should test the
system getpass() to see if it returns more than 8 chars - and if not,
unconditionally compile the replacement code.  That way, we will either
have a working getpass(), or fail to build. 

Andrew Bartlett



More information about the samba-technical mailing list