[Date Prev][Date Next]
Re: Antwort: Re: Antwort: Re: Need migrationhelp for 220.127.116.11.4.1.1418.104.22.168.5 because of bug in slapcat
Frank Offermanns wrote:
> > I hope this makes things clearer.
> > Tell me if I should make an ITS.
> That's called "Base64 encoding". Go decode your encoded value, I think
> you'll be happy.
The current ldif exports are not encoded, so what should I decode?
The old was, as it should be.
To be more clear:
With OpenLDAP 2.3.35 I could make a slapcat and then a slapadd and had
no problems because the ldif generated of slapcat was Base64 encoded for
attributes of syntax 22.214.171.124.4.1.14126.96.36.199.5, so slapadd was able
to import it.
With OpenLDAP 2.3.39, 40 and 41 the slapcat generates a "bad" ldif,
where binary content of the syntax 188.8.131.52.4.1.14184.108.40.206.5 is not
Base64 encoded. So slapadd is not able to import it.
OpenLDAP 2.3.41 is over 7 years old. Why are you using such an old release?
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/