Jeremy Allison
1999-Feb-09 18:10 UTC
Long passwd not working with HPUX10.20 and Samba 2.0.2 (PR#13591)
J.P.M.v.Itegem@ele.tue.nl wrote:> > About a month ago I reported a bug in Samba 2.0.0 that users with > passwords longer than 8 characters could not logon. > I now found out that this is still the case in Samba 2.0.2 > Note: Samba 1.9p18 was OK > > For the record: > I am using > HPUX 10.20, > Samba 2.0.2, > GCC 2.7.2.3, > PlaintextPasswords > > I hope you can fix it > Regards > Jos >I'm going to need some help fixing it. The problem is that Samba 1.9.18 hand-selected the HPUX authentication mechanism to use in the Makefile, Samba 2.x tries to auto-detect it and seems to get it wrong on HPUX only. Can someone look at the file source/tests/cryypttest.c and try this test on their system. This is the way Samba decides if a crypt on a system needs to have the salt truncated to 2 characters. The trouble is, when I test this on my HPUX10.20 system it tells me that the salt doesn't need to be truncated (it's using standard crypt, not bigcrypt). Now with Samba 1.9.18x there was a hack that forced the salt to be truncated - but this then broke FreeBSD (which must not have the salt truncated). We went around in a circle in the 1.9.18x series with each subsequent release breaking either HPUX or FreeBSD until we figured out what was going on - which is why I don't want to fix it the same way in 2.x. The problem is HPUX seems to have a couple of different ways of doing plaintext password authentication, the standard crypt mechanism, the bigcrypt mechanism. Samba 2.x has to pick one, and for some HPUX systems it seems to be picking the wrong one.... Regards, Jeremy Allison, Samba TEam. -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. --------------------------------------------------------
After upgrading from Samba version 1.9.18p8 to Samba 2.0.0 I experienced that every samba process was owned by root, so all users gained root-access to every file-system. I tried to upgrade to Samba 2.0.2 but the problem still was the same. I'm running AIX 3.2.5 on a RS 6000 / 530 and I have never seen this problem on previous versions. I am now running Samba version 1.9.18p8 and everything works fine. I have not changed anything in my smb.conf -file. If anyone have experienced similar trouble, or have a clue how this could be solved, please let me know. Olav
Dirk De Wachter
1999-Feb-10 14:04 UTC
Long passwd not working with HPUX10.20 and Samba 2.0.2 (PR#13591)
> Can someone look at the file source/tests/cryypttest.c and > try this test on their system. This is the way Samba > decides if a crypt on a system needs to have the salt > truncated to 2 characters. > > The trouble is, when I test this on my HPUX10.20 > system it tells me that the salt doesn't need to be > truncated (it's using standard crypt, not bigcrypt).Same here, both with bigcrypt and crypt. The problem may be that HPUX10.20 is just a version number. It might be more important to look at patch levels of the libraries. My libc libs are from December 23, 1997. The libsec libraries are from June 3 (archive) or 4 (shared) 1997. 'what (1)' strings: libc: PATCH-PHCO_13626 for 10.20 libsec: $Revision: 78.7.1.3 $> The problem is HPUX seems to have a couple of different > ways of doing plaintext password authentication, the > standard crypt mechanism, the bigcrypt mechanism.I saw no difference for both mechanisms. I compiled the crypttest.c with and without -DHAVE_BIGCRYPT and with and without the libsec library. Best regards, Dirk De Wachter *--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* Dirk De Wachter, MScEE, MScBME, PhD mailto:Dirk.DeWachter@rug.ac.be scientific researcher, systems administrator http://navier.rug.ac.be Hydraulics Laboratory, Ibitech, University of Gent voice:+32 9 264 3281 Sint-Pietersnieuwstraat 41, B-9000 Gent Belgium faxto:+32 9 264 3595 ~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~--~