slapd-sock: extensions always UTF-8

[Michael Ströder]

Content preview: HI! Are these extensions guaranteed to be always sent by back-sock
as raw UTF-8 in one line? Or does the listener also has to handle base64
encoding and line-folding like in LDIF for these extension lines? [...]

Content analysis details: (-2.6 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust
[213.240.180.113 listed in list.dnswl.org]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]

HI!

Are these extensions guaranteed to be always
sent by back-sock as raw UTF-8 in one line?
Or does the listener also has to handle
base64 encoding and line-folding like in LDIF for these extension lines?

binddn: <bound DN>
peername: IP=<address>:<port>
ssf: <SSF value>
connid: <connection ID>

Ciao, Michael.