samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2010-05-18	Finish removal of iconv_convenience in public API's.	Jelmer Vernooij	1	-2/+2

2010-04-29	s4/dsdb: schemaInfo revision may be 0	Kamen Mazdrashki	1	-5/+1
	In case schemaInfo value is still not set, WinAD supplies schemaInfo blob with revision = 0 and GUID_ZERO
2010-04-29	s4/dsdb: remove unused dsdb_schema_info_create() function	Kamen Mazdrashki	1	-35/+0

2010-04-29	s4/dsdb: Update Schema cache with updated schemaInfo value	Kamen Mazdrashki	1	-4/+9
	Error checking is simplified and my leave leeks. I did it this way to make code more readable, and if we get error in those lines, it will be WERR_NOMEM in which case we are in a much deeper troubles than delayed freeing of few bytes.
2010-04-29	s4/samldb: Create initial schemaInfo value if it doesn't exists yet	Kamen Mazdrashki	1	-7/+30

2010-04-29	s4/dsdb: Use default schemaInfo value when no such value is given	Kamen Mazdrashki	1	-0/+22
	Having no value for schemaInfo is totally OK as it turns out. In such cases, we should use a default value with all fields set to 0.
2010-04-29	Revert "s4/dsdb: Set schemaInfo attribute value during provisioning"	Kamen Mazdrashki	1	-49/+0
	This reverts commit 8149094eddebd9a0e8b7c123c2ed54d00164bb26. Windows implementation does not set schemaInfo attribute value until first Schema update request. This way, newly provisioned forest returns no schemaInfo value. I think it won't be bad for us to have this value preset, but I want to mimic Win AD behavior as close as possible.
2010-04-21	s4-schema: allow revision numbers of zero	Andrew Tridgell	1	-6/+3
	w2k8r2 sends a revision of zero in the initial schema replication during a net vampire Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2010-04-13	Revert "s4:prefer "samdb__dn" basedn calls over the "ldb_get__dn" functions"	Matthias Dieter Wallnöfer	1	-2/+2
	We should use the "ldb_get_*_basedn" calls since they are available in the LDB library.
2010-04-10	s4:dsdb Don't use the permissive modify control on schemaInfo updates	Andrew Bartlett	1	-2/+2
	The use of 'replace' is enough to wipe out the old value, whatever it is, we don't need to set 'permissive modify' too. Additionally, this seems to be causing trouble for the OpenLDAP backend Andrew Bartlett
2010-04-09	s4/dsdb: Set schemaInfo attribute value during provisioning	Kamen Mazdrashki	1	-0/+49
	After provisioning new Forest, schemaInfo should be set to a value with revision=1 and current invocation_id
2010-04-09	s4/dsdb: split writing of schemaInfo blob in two parts	Kamen Mazdrashki	1	-21/+46
	ldb_msg preparation is moved into separate function so that it can be used for implementing schemaInfo updates both on module stack (dsdb_module_... functions) and directly on ldb_context
2010-04-09	s4/dsdb: Let caller to control if valid invocationId is critical or ↵	Kamen Mazdrashki	1	-1/+6
	zero-guid is acceptable
2010-04-09	s4/dsdb: dsdb_schema_info object implementation	Kamen Mazdrashki	1	-0/+383