Re: Binary attribute value truncated on replication (ITS#2932)

[Kurt@OpenLDAP.org]

Note that we generally don't chase down bugs in
historical versions of OpenLDAP Software.  Suggest you
consider updating to a current release (2.2.5 or 2.1.26)
or the current stable (2.1.25) version of OpenLDAP Software.

If you are able to duplicate this problem with a newer
version, please provide enough information so that a developer
can reproduce the problem.  That information should include
the schema descriptions (in slapd.conf(5) form), LDIF input
to the master, the intermediate replog information, as well
as LDIF output from the slave.

Kurt

At 04:20 AM 1/23/2004, gergely.fejos@office.ksh.hu wrote:
>Full_Name: Gergely Fejös
>Version: 2.0.23
>OS: HP-UX B.11.00, B.11.11
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (193.6.239.25)
>
>
>An LDAP object containing an attribute defined as BINARY in the schema was added
>to the master LDAP database. When this object was replicated by slurpd, and the
>object was written into the slave LDAP, the value of this binary attribute was
>truncated to 28 bytes, as it can be read from the ldapsearch output. If anyone
>knows a solution or a workaround, please write me.