SYSKEY, TNG freeze, 2.0.x->TNG merge and other thoughts

[Nicolas Williams]

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.