The branch, master has been updated
       via  0a78c57 s4-dsdb: Ensure we permit multi-valued backlinks on 
single-valued attributes
      from  016a8d2 s3-printing: vfs_connect prior to driver/dfs IO

http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 0a78c57be64c3b47b0a685c248c7738559a64bf0
Author: Andrew Bartlett <[email protected]>
Date:   Tue Mar 1 22:47:33 2011 +1100

    s4-dsdb: Ensure we permit multi-valued backlinks on single-valued attributes
    
    This was already done in repl_meta_data, but it needs to be done here
    as well to cope with Windows 2000 level links.
    
    Andrew Bartlett
    
    Autobuild-User: Andrew Bartlett <[email protected]>
    Autobuild-Date: Wed Mar  2 02:03:58 CET 2011 on sn-devel-104

-----------------------------------------------------------------------

Summary of changes:
 source4/dsdb/samdb/ldb_modules/linked_attributes.c |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)


Changeset truncated at 500 lines:

diff --git a/source4/dsdb/samdb/ldb_modules/linked_attributes.c 
b/source4/dsdb/samdb/ldb_modules/linked_attributes.c
index 324faa2..393f00f 100644
--- a/source4/dsdb/samdb/ldb_modules/linked_attributes.c
+++ b/source4/dsdb/samdb/ldb_modules/linked_attributes.c
@@ -975,6 +975,13 @@ static int la_do_op_request(struct ldb_module *module, 
struct la_context *ac, st
                ret_el->values[0] = 
data_blob_string_const(ldb_dn_get_extended_linearized(new_msg, ac->del_dn, 1));
        }
 
+       /* a backlink should never be single valued. Unfortunately the
+          exchange schema has a attribute
+          msExchBridgeheadedLocalConnectorsDNBL which is single
+          valued and a backlink. We need to cope with that by
+          ignoring the single value flag */
+       ret_el->flags |= LDB_FLAG_INTERNAL_DISABLE_SINGLE_VALUE_CHECK;
+
 #if 0
        ldb_debug(ldb, LDB_DEBUG_WARNING,
                  "link on %s %s: %s %s\n",


-- 
Samba Shared Repository

Reply via email to