post 3.0 idmap+winbindd_passdb requirements [was Re: refactoring idmap code in smbd]

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here's are the conditions under which I would accept 
idmap+winbindd_passdb (a.k.a. the sam) in the post 3.0 
codebase:

  1)  The sam is presented as a complete working package.  
      Not half done components.

  2)  It must co-exist with the current implementation
      of winbindd_acct.  Selecting the idmap+winbindd_passdb
      code should be done by setting 'enable sam = yes' in 
      smb.conf.  Default is disabled initially.  

  3)  no idmap lookups in smbd initially.  Still go through 
      winbindd.  This means that the current sid_to_uid() 
      would become

      if ( !winbind_sid_to_uid() ) {
         if ( !lp_enable_sam() && local_sid_to_uid() )
	   return success;

         return failure;
      }

      I don't want to hear artifical arguments about performance
      without a complete, working solution to evaluate.  
      Correctness first. Performance later.

  4)  winbindd_passdb can be no more disruptive to winbindd than
      msrpc_methods or ads_methods.


To relieve patch pressure on this, we'll plan to get HEAD back 
in shape and sync'd up with 3.0 very soon.




cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE/Db+KIR7qMdg1EfYRAlsKAKCyapfIbsT30Sb3Wrez0BYR4Y+CgQCfep0y
O/sXpk3CEeIdZTtnusoOXts=
=Cpw1
-----END PGP SIGNATURE-----