James Sumners

An MRE would include: 1. A server instance that is just enough to cover the issue 2. A client instance that sends an equivalent message that triggers the issue

I recommend using [Wireshark](https://www.wireshark.org) to inspect the conversation between your client and server to determine what message is being sent that causes the crash.

Please review my original response to this thread. Needing to setup extra services and user accounts is not viable.

It's quite difficult to translate these hex strings back to human readable LDAP messages, and it's just more effort than I am willing to put in. Can you please provide...

This is the minimal reproduction: ```js 'use strict' const ldapjs = require('ldapjs') let client const server = ldapjs.createServer() server.bind('ou=example', (req, res, next) => { res.end() return next() }) server.listen(1666, '127.0.0.1',...

https://github.com/ldapjs/node-ldapjs/blob/6ceef130145b38ba33b5ccc798bf49304194fb0f/LICENSE#L13-L19 No one is required to give you free support. I worked quite diligently to guide you toward finding the cause, and will provide guidance in solving it. Those who...

Whether or not you agree: 1. We need a reproduction that can be added as a failing test to the test suite in order to ensure that any fix is...

Can you please provide examples of error messages you are talking about? I do not understand the issue.

Please provide the full stack trace for the errors instead of just the `message` property.

Please file a different issue if you think binding is not working correctly. This issue is about the information in the error.