[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: slapcat generate extra "space" characters in LDIF output
- To: elecharny@apache.org
- Subject: Re: slapcat generate extra "space" characters in LDIF output
- From: "Mark J. Reed" <markjreed@gmail.com>
- Date: Thu, 9 Sep 2010 12:46:09 -0400
- Cc: openldap-technical@openldap.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oLNNfvtRxaG2aviFSIS3w62+P59K1M/WUgX87eoRsKk=; b=AuyzW8d+E52ujjYthbXY4ONviHNQPuMSDzdEj5Lf9fr6mscFDj2px2AudvoN7rXSbl wxD2gHa/GXpDg9mLN6mD8xYbsjfHVYbLnhWj1R/GiAXzLXwhx4bj9sRfun1A2Bet0nCq 1WWYLuFdEVr8srG+gZi1nAQuTGe4c2U/fMkGo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iGd4jY2BKbA+TpNeFjmGUkCAj3aEjY2H+0EXfzAt66bMvPhxZJ5g0CVK2ifRvj0PCp OtHJPPF9gk1Zkf2Rd/6uoGUFu0Ro2VEhFO73osnOzJ8YaWsvM4OwrCRPpTFsq2pDw20H foR4bGg4fY03ik19ZKp4MpSR3O7cuEbhPXqM4=
- In-reply-to: <4C890C3E.5080701@gmail.com>
- References: <4C878B00.4090200@esiee.fr> <87r5h4tkxu.fsf@magenta.l4b.de> <4C890C3E.5080701@gmail.com>
On Thu, Sep 9, 2010 at 12:33 PM, Emmanuel Lecharny <elecharny@gmail.com> wrote:
> 10) When an attrval-spec, distinguishedName, or rdn is base64-
> encoded, the encoding rules specified in [5] are used with the
> following exceptions: a) ***The requirement that base64 output
> streams must be represented as lines of no more than 76
> characters is removed.***
Point. Based on a quick reread of RFC 2849, LDIF doesn't mandate line
wrapping. But it does explicitly allow it, so tools that process LDIF
need to be able to deal with wrapped lines.
And it occurs to me that the unfold script can also be done a perl one-liner:
perl -pe 'BEGIN { undef $/; } s/\n //gms'
--
Mark J. Reed <markjreed@gmail.com>