Convert::ASN1, Convert::BER question (2)

Folks, Shouldn't have hit send so quickly. A couple more things of interest in comparing the dump routines of Convert::ASN1 and Convert::BER. I realize these are for *debug only*, per the source, but ... In Convert::BER->dump(), I think that most of the addresses of the contents of "complicated

Convert::ASN1 dump question

Folks, While fiddling with Convert::ASN1's wonderful dump routine, asn_dump(), and Convert::BER's equally nice dump() routine, I came across the following "huh?"... [Convert::BER->dump() v 1.3101] ... 0060 13 35: UNIVERSAL [19] ... 0097 30 13: SEQUENCE { 0099 06

Re: unstable openldap after using Net::Ldap perl module

You might also need to worry about referential integrity, although I have only seen this hose up secondary objects that referred to the now-deleted dn. Examples include the "manager=", "secretary=", or "owner=" attributes, for instance. Where we (used to) get bit by this was in group membership l

binary AD attributes?

Folks, This should be simple, but I can't find the answer in the FM's... I do a search, get a set of entries as a result. Now I want to "dump" them. When printing, how do I simply distinguish a binary attribute? There are a bunch of these things in the AD schema... rnd

strange unbind results

Folks, Am looking for hints as to why this is going on. I have a script that verifies object replication to a bunch of slave ldap servers. It does this by trying to do a bind with full DN and userPassword. The script gives different results between the master, a Critical Path 3.1.4 version, and