mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-30 08:32:05 +00:00
8a0e5f822b
When the LDAP response is parsed, the message length is not properly decoded. While it works for LDAP servers encoding it on 1 byte, it does not work for those using a multi-bytes encoding. Among others, Active Directory servers seems to encode messages or elements length on 4 bytes. In this patch, we only handle length of BindResponse messages encoded on 1, 2 or 4 bytes. In theory, it may be encoded on any bytes number less than 127 bytes. But it is useless to make this part too complex. It should be ok this way. This patch should fix the issue #1390. It should be backported to all stable versions. While it should be easy to backport it as far as 2.2, the patch will have to be totally rewritten for lower versions. |
||
|---|---|---|
| .. | ||
| 1be_40srv_odd_health_checks.vtc | ||
| 4be_1srv_health_checks.vtc | ||
| 4be_1srv_smtpchk_httpchk_layer47errors.vtc | ||
| 40be_2srv_odd_health_checks.vtc | ||
| agent-check.vtc | ||
| common.pem | ||
| http-check-expect.vtc | ||
| http-check-send.vtc | ||
| http-check.vtc | ||
| http-monitor-uri.vtc | ||
| ldap-check.vtc | ||
| mysql-check.vtc | ||
| pgsql-check.vtc | ||
| redis-check.vtc | ||
| smtp-check.vtc | ||
| spop-check.vtc | ||
| ssl-hello-check.vtc | ||
| tcp-check_min-recv.vtc | ||
| tcp-check_multiple_ports.vtc | ||
| tcp-check-ssl.vtc | ||
| tcp-checks-socks4.vtc | ||
| tls_health_checks.vtc | ||