Hi...
I'm the current debian maintainer for the debian python-ldap package.
This bug has been sitting in our BTS for a while:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D76722&repeatmerged=3Dy=
es
--- SNIP ---
This piece of code might not be correct but it certainly should not
make python segfault:
import ldap
class ldapObject:
def __init__(self,dn=3D""):
'''ldapObject constructor.'''
self.dn=3Ddn
self.attr=3D{}
db=3Dldap.open("db.mors.wiggy.net",389)
db.simple_bind("cn=3Dadmin,ou=3DPeople,dc=3Dmors,dc=3Dwiggy,dc=3Dnet", "1=
2345")
o=3DldapObject("uid=3Dtst,ou=3DPeople,dc=3Dmors,dc=3Dwiggy,dc=3Dnet")
o.attr["objectClass"]=3D"top"
o.attr["uid"]=3D"tst"
db.add_s(o.dn, o)
--- END SNIP ---
I just checked and it still causes problems with 2.0.0-pre05. (though=20
you may need to change db.mors.wiggy.net to something you can=20
actually contact).
A patch for this issue (against 2.0.0-pre04, but still applies=20
correctly against 2.0.0-pre05), the correctness of which I am not=20
totally certain, is attached. Could you please check it and apply it=20
to your source tree?
Thanks,
Peter
--
pe...@ha...
GPG key fingerprint:
C746 38A9 D3E4 A171 FB6A 56D4 5E30 DFCC BE11 F437 |
