Upgrade issue with 3.0.21b->3.0.22

[Gerald (Jerry) Carter]

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

Gerald (Jerry) Carter wrote:

> Whatever we do, we will need to plaster an upgrade HOWTO
> in some very visible places (not just the release notes).
> Other than the primary group SID and object ACLs on
> client NTFS partitions, what are the other problematic cases?
> 
> Can we simply ignore the primaryGroupSID from the passdb objects
> and force the Domain Users SID (requiring that the admin
> has setup a mapping for this one group)?  This would be in the
> NT_USER_TOKEN only and not affect the Unix token.

Volker,

OK.  Let's assume that we get everythign worked on a DC
and standalone installation.  A Samba member server in a domain
can either (a) run winbindd, or (b) share Unix users and groups
with the DC via NSS.  The current 'winbind trusted domains only'
is a hack and only really works with users and not groups.

Therefore I would really like to finish the \unixinfo pipe
you started since IMO it is a piece of the complete deployment
solution.  Any objections there ?





cheers, jerry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD6hzNIR7qMdg1EfYRAtaUAKDQiD94GYZ7dTz3UaOGJPatm+QM0wCgofLg
FTzboTxfg3uLnY31zzKM8mw=
=gxgp
-----END PGP SIGNATURE-----