diff options
| author | Stefan Metzmacher <metze@samba.org> | 2014-03-13 23:12:39 +0100 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2014-05-02 01:19:19 +0200 |
| commit | 709ed040ec161e99b3c1f7076eac4a631149f64a (patch) | |
| tree | d78a6f91d322e292608e7520003c609943007d99 /python/samba/netcmd/ldapcmp.py | |
| parent | 821d7dc7b33598f72c4518f8975073b058df5960 (diff) | |
| download | samba-709ed040ec161e99b3c1f7076eac4a631149f64a.tar.gz samba-709ed040ec161e99b3c1f7076eac4a631149f64a.tar.xz samba-709ed040ec161e99b3c1f7076eac4a631149f64a.zip | |
dbchecker: verify and fix broken dn values
With older Samba versions (4.0.x) the following could happen:
- On account was created on DC1
- It was replicated to DC2
- The connection between the dcs is offline
- The account gets modified on DC2
- The account gets deleted on DC1
- The connection becomes online again
- DC1 replicates the modification from DC2,
this resets the dn to the original value.
'name' and 'cn' are correct (with '\nDEL${GUID}'),
but 'dn' is wrong.
- DC2 replicates the deletion from DC1.
this doesn't include a changed dn as DC1
had a bug.
'name' is correct (with '\nDEL${GUID}'),
but 'cn' and 'dn' are wrong.
Bug: https://bugzilla.samba.org/show_bug.cgi?id=10536
Change-Id: Ia70a6c12e0ff0d4c2c8100cb1d8f3c6422b65591
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Diffstat (limited to 'python/samba/netcmd/ldapcmp.py')
0 files changed, 0 insertions, 0 deletions