NIS+ support in samba-2.0.5a
toby at cogsci.ed.ac.uk
Tue Oct 26 11:43:00 GMT 1999
> We also run in this problem. The application does not a 'keylogin'
> (getpublickey, getsecretkey, key_setsecret, ...)
> Solaris telnet does it, latest version wuftd also.
> For the qulacomm pop server, recompile with the SECURENISPLUS
> option. (this is also an exemple of what sould be changed in the
> I've not run in this problem with SAMBA, but our samba production
> server does not run Solaris 2.7 yet.
Yes, this is what we've assumed. We've started investigating with
Sun's own pop and imap daemons to see how they behave.
Is anyone else running SAMBA under Solaris 2.7 and also seeing this
problem? It would be nice to be able to compile keylogin support into
> My understanding is that
> NISPLUS password database is using a nisplus table for
> the NT/LANMan ENCRYPTED passwd instead of the samba/private/smbpasswd
OK, great. That does explain things - we're still using plain text
passwords. The only reason for not moving to encrypted ones is the
niggly problems with having two password tables.
More information about the samba