s4:LDB/LDAP - Re-allow renames

Andrew Bartlett abartlet at samba.org
Sat Oct 3 02:14:45 MDT 2009

On Fri, 2009-10-02 at 14:30 -0500, Matthias Dieter Wallnöfer wrote:

>     The main problem is that the "rdn_name" module launches on a
> rename request also
>     a modification one with the "special attributes" which can't be
> changed directly.
>     An introduced flag helps to bypass the restriction.


While I realise this has already been reverted, if this flag fixed
anything, then we have far more serious issues.  It means that some part
of the module stack is calling back to the top of the stack and doing a
ldb_modify().  The rdn_name module simply calls the next module with the
modify (ldb_next_request()), and will not foul it's own check here. 

I hope this helps you find the real issue here.


Andrew Bartlett

Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Cisco Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20091003/7823d62f/attachment.pgp>

More information about the samba-technical mailing list