In case of indexing conflicts, the ldb error message could output the conflicting value to help identifying the source of the conflict.
Created attachment 7851 [details]
patch against ldb-1.1.9
Hmmm. My only issue with this patch - is "el->values[v_idx].data" guaranteed to be a printable string ?
I'm also wondering if we could be disclosing secret information this way.
Currently unique indexes are on mundane things, and we don't have read access controls (except for a static list of secrets), but both of these things could change.
If you do have read access to the attributes, finding out manually what you conflicted with shouldn't be too hard.
Fixed by 2277301e46614154977b242d38669673eee5fe25 in master for Samba 4.7
I log more detail to the error log, but leave the remote error string vague for confidentiality.