Open GoogleCodeExporter opened 9 years ago
It's intended work.
We blocks DN attribute change by mass update by default. (objectClass is also
blocked
by default) The current update_attributes(:id => ...) behavior is a bug.
It seems that RDN change by mass update is dangerous. If it's not dangerous, we
will
not block DN attribute change by mass update by default.
Original comment by kou...@gmail.com
on 12 Oct 2009 at 2:11
Hi koutou.
Sorry, Now I'm very busy with project...
I think change RDN by mass update not so dangerous for 'hdb' database;
But how I remember 'bdb' database can have problems with this..
Problem was described in thread: Question about children with different
objectClass
http://rubyforge.org/pipermail/ruby-activeldap-discuss/2009-June/000833.html
Original comment by Alexey.Chebotar@gmail.com
on 14 Oct 2009 at 10:58
I worry about dangerousness on programmer not LDAP backend.
It's dangerous that mass update causes many programming misses or security
problems.
What do you think about the dangerousness?
Original comment by kou...@gmail.com
on 16 Oct 2009 at 12:18
Original issue reported on code.google.com by
Alexey.Chebotar@gmail.com
on 10 Oct 2009 at 9:34