Linux as an NT CLIENT

[Mayers, P J]

Yeh, saw that after I pulled the TNG code down. Cool.

Cheers,
Phil

=====================

The world is divided into two kinds of people, those who divide the world
into two kinds of people, and those who don't... 

-----Original Message-----
From: Luke Kenneth Casson Leighton [mailto:lkcl at samba.org]
Sent: Tuesday, February 29, 2000 7:58 PM
To: Multiple recipients of list SAMBA-NTDOM
Subject: RE: Linux as an NT CLIENT


luke howard has already written a sursldap, it's incredibly simple: it's a
switch statement around two function calls.

so it's been done.

luke

On Wed, 1 Mar 2000, Mayers, P J wrote:

> I'm well aware of the need for s SURS implementation. In fact, if/when the
> API settles down, pulling the SID->uid/gid mapping out of an LDAP
directory
> is something I'd like to look at.
> 
> Cheers,
> Phil
> 
> -----Original Message-----
> From: Luke Kenneth Casson Leighton
> To: Multiple recipients of list SAMBA-NTDOM
> Sent: 29/02/00 16:58
> Subject: RE: Linux as an NT CLIENT
> 
> On Wed, 1 Mar 2000, Mayers, P J wrote:
> 
> > Yes, still need a passwd/NIS entry. IIRC there was something under
> > development called winbind, which is the equivalent for ypbind for an
> NT
> > domain, rather than NIS. Very nice. But it was dependent on SURS, and
> hence
> > probably TNG. Again, I don't know the progress.
> 
> yeah, tim's working on it.
> 
> actually, absolutely _Everything_ is dependent on a decent SURS
> implementation, and we don't have one.
> 
> and no, dammit, the current one _isn't_ good enough.  however, as i was
> explaining to tim (it took a couple of days, and his code got a _lot_
> simpler when he got it), it's not the responsibility of samba,
> pam_ntdom,
> pam_smb, winbind, pam_smbpass, or anything BUT surs itself to solve the
> problem of mapping uids/gids and sids.
> 
> luke
> 
> > 
> > -----Original Message-----
> > From: Jay Thomas
> > To: Multiple recipients of list SAMBA-NTDOM
> > Sent: 2/29/00 1:01 AM
> > Subject: Re: Linux as an NT CLIENT
> > 
> > Jonathan Hutchins wrote:
> > 
> > > > On Sat, 19 Feb 2000, Jonathan Hutchins wrote:
> > >
> > > >> What are the critical steps in getting a Samba machine to join
> the
> > > >> domain and access shares?
> > >
> > > And Luke Kenneth Casson Leighton <lkcl at samba.org> rather sparsely
> > replied:
> > >
> > > > pam_ntdom.
> > >
> > > Which migh possibly be a compile-time option?  Not currently doc'ed
> as
> > a
> > > configuration keyword.
> > >
> > > >From the looks of the list, there are some problems with the
> > > authenticate-the-linux-user-from-the-NT-PDC code, yet Jason Holland
> > says "I
> > > have several samba boxes joined and authenticating to NT PDC's".
> > >
> > > There appears to about 1/3 of a page of documentation on this.  I'd
> > gladly
> > > write a HOWTO if someone could take the time to elaborate a bit
> more.
> > I've
> > > got most of the rest of the functionality of an NT Client working,
> > just need
> > > the authenticate-from-NT part.
> > 
> > Do you need to have a passwd file entry for each user when they
> > authenticate of
> > a NT-PDC?
> > 
> > Anyone got this to work w/ HPUX 10.20 or 11? (they seem to have an
> older
> > PAM version than is standard)
> > 
> 
> <a href=" mailto:lkcl at samba.org" > Luke Kenneth Casson Leighton    </a>
> <a href=" http://cb1.com/~lkcl"  > Samba and Network Development   </a>
> <a href=" http://samba.org"      > Samba Web site                  </a>
> <a href=" http://www.iss.net"    > Internet Security Systems, Inc. </a>
> <a href=" http://mcp.com"        > Macmillan Technical Publishing  </a>
>  
> ISBN1578701503 DCE/RPC over SMB: Samba and Windows NT Domain Internals
> 

<a href=" mailto:lkcl at samba.org" > Luke Kenneth Casson Leighton    </a>
<a href=" http://cb1.com/~lkcl"  > Samba and Network Development   </a>
<a href=" http://samba.org"      > Samba Web site                  </a>
<a href=" http://www.iss.net"    > Internet Security Systems, Inc. </a>
<a href=" http://mcp.com"        > Macmillan Technical Publishing  </a>
 
ISBN1578701503 DCE/RPC over SMB: Samba and Windows NT Domain Internals