Upgrade issue with 3.0.21b->3.0.22

Gerald (Jerry) Carter jerry at samba.org
Wed Feb 8 13:56:24 GMT 2006


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

Volker Lendecke wrote:

> One way around this is to have a one-shot upgrade script and
> never look back again. An idea I don't really like.
> 
> Another possibility would be a parameter where we have to
> choose the default very carefully. The problem here is that
> I just removed the 'enable rid algorithm' parameter...
> 
> How should we handle this? Any opinions?

Volker,

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.




cheers, jerry

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

iD8DBQFD6fiIIR7qMdg1EfYRAiMZAKCyJHsb5fM/suJV4Bw8EZBAx1onzgCfRSt5
YPJbKOrxcs+3hF6LgAhFqfk=
=pLHn
-----END PGP SIGNATURE-----


More information about the samba-technical mailing list