Howard Chu wrote:

michael@stroeder.com wrote:

...

michael@stroeder.com wrote:

...

Null-bytes really needed?

Hmm, with null-bytes the wrong result code is returned to the LDAP cli=

ent.

...

Without null-bytes the correct result code is returned to the client b=

ut slapd

...

complains about unknown string:

'RESULT\nmsgid: 1\ncode: 49\nmatched: uid=3Dwuqww,cn=3Dampua,ou=3Dampu=

a\ninfo:

...

NOK\n\n'

results in log message:

559174df str2result (msgid: 1 code: 0

) unknown 559174df str2result ( ) unknown

=20 I would almost suspect you were running on Windows. None of the behavio=

r

you're reporting occurs for me using the searchexample.pl script.

Your script does not return any real 'RESULT..' responses. I also have less issues when just returning 'CONTINUE\n'.

Sounds like your problem is a python runtime configuration, not a slapd=

bug.

Not on Windows and no run-time configuration involved.

Look at the raw string representations I've posted. That string goes dire= ctly to SocketServer.BaseRequestHandler.request.sendall(response_str).

Can I raise the debug level? Log level trace does not really show the ori= ginal byte sequence received by the external listener.

Ciao, Michael.