alexz at visp
Jul 22, 2012, 11:30 PM
Post #4 of 5
------- You are receiving this mail because: -------
[Bug 1273] `ldapauth` fails when TLS is enabled
[In reply to]
You are on the CC list for the bug.
--- Comment #3 from Alexander Zagrebin <alexz [at] visp> 2012-07-23 07:30:54 ---
(In reply to comment #2)
> Which LDAP server are you using?
> The code change you use says to not use TLS if already *authenticated* to the
> server; that may be a decent approximation, while the ldap_* options are not
> expanded, but I'm reluctant to use it as-is because it means that if those
> options become expanded, a configuration which allows anonymous binds without
> TLS but is supposed to use TLS for an authenticated bind would avoid TLS and
> this would then become a security bug.
Hm-m-m. lcp->bound will be set to TRUE after any successful bind, including the
anonymous (not authenticated) bind. So the patch prevents starting of TLS if we
are already successfully connected to the server (it's a case when exim uses
When looking in the cache, exim checks an IP address and corresponding port
only and not checks any options.
So, imho, it is impossible to have two connections (unprotected and protected
via TLS) to the same host/port in the same time.
> Could you include a debug trace showing the lookups failing for you, with
> sensitive data anonymised? I'm not in a situation to set up a decent test this
> weekend to replicate myself.
The log is attached.
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##