SYSKEY, TNG freeze, 2.0.x->TNG merge and other thoughts
Luke Kenneth Casson Leighton
lkcl at samba.org
Tue Feb 8 21:35:09 GMT 2000
On Wed, 9 Feb 2000, Charles N. Owens wrote:
> Is there any update available as to when Luke Howard's
> SAM-via-LDAP-with-win2k-schema will make into the codebase (either TNG or
> TNG-post-merge) ? Getting a somewhat finalized schema in place seems to me
./configure --with-nt5pdap
or:
./configure --with-nt5pdap --with-sam-pwd=nt5ldap
it's experimental and subject to change.
> to be a critical milestone for obvious reasons. I need to roll out some more
> implementations and would much prefer to use the new schema (as would
> everyone I'm sure ;-).
>
> Charles
>
> Nicolas Williams wrote:
>
> > Gratouitous advice follows.
> >
> > - SYSKEY
> >
> > I'm now for it as Luke's LDAP/NIS/other name services argument is a
> > winning one. The /etc/shadow approach should still be supported and
> > used where no such cleartext protocols are in use.
> >
> > The question now should be one of scheduling/prioritizing. SYSKEY is
> > not needed urgently to allow TNG to make progress, unless Luke Howard
> > thinks otherwise (he's doing the SAM-via-LDAP-with-win2k-schema work).
> >
> > - TNG code freeze
> >
> > Don't do it yet; wait a few more weeks. So much progress is taking
> > place that it seems worthwhile to wait a bit longer.
> >
> > - 2.0.x->TNG merge
> >
> > This should be easy, actually: take smbd code from 2.0.x as is, drop
> > all the MSRPC code save for the loopback to MSRPC daemons code.
> >
> > That's it.
> >
> > TNG seems to be much further ahead on the MSRPC issues, which means
> > there's no merge to do from 2.0.x there.
> >
> > Same thing with utilities such as rpcclient, though smbclient and
> > nmblookup might be best taken from 2.0.x.
> >
> > I think it's safe to say that TNG is so jam-packed with good ideas that
> > it will become the next Samba. But then, that's just a view from the
> > sidelines... others may differ on that...
> >
> > Nico
> > -DISCLAIMER: an automatically appended disclaimer may follow. By posting-
> > -to a public e-mail mailing list I hereby grant permission to distribute-
> > -and copy this message.-
> >
> > This message contains confidential information and is intended only
> > for the individual named. If you are not the named addressee you
> > should not disseminate, distribute or copy this e-mail. Please
> > notify the sender immediately by e-mail if you have received this
> > e-mail by mistake and delete this e-mail from your system.
> >
> > E-mail transmission cannot be guaranteed to be secure or error-free
> > as information could be intercepted, corrupted, lost, destroyed,
> > arrive late or incomplete, or contain viruses. The sender therefore
> > does not accept liability for any errors or omissions in the contents
> > of this message which arise as a result of e-mail transmission. If
> > verification is required please request a hard-copy version. This
> > message is provided for informational purposes and should not be
> > construed as a solicitation or offer to buy or sell any securities or
> > related financial instruments.
>
> --
> -------------------------------------------------------------------------
> Charles N. Owens Email: owensc at enc.edu
> http://www.enc.edu/~owensc
> Network & Systems Administrator
> Information Technology Services "Outside of a dog, a book is a man's
> Eastern Nazarene College best friend. Inside of a dog it's
> too dark to read." - Groucho Marx
> -------------------------------------------------------------------------
>
>
<a href="mailto:lkcl at samba.org" > Luke Kenneth Casson Leighton </a>
<a href="http://www.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
More information about the samba-ntdom
mailing list