Hi, Steve, thanks for your helpful reply.
On Saturday 05 April 2008 02:20, Steve Langasek wrote:
> I don't think the
> current behavior of this file *is* a sensible default, because ldapi:/// is
> missing; but ldap:/// ldapi:/// should be a sensible default IMHO,
> excluding ldaps:/// because TLS should be sufficient for the common case.
> You do mention in the bug report that you specifically care about enabling
> ldaps:///, can you explain why this is needed in your
> environment?
> What clients do you have that can't use TLS?
I suspect this is for historic reasons, can someone who actually knows the
history please confirm or deny this?!
If so, we should switch to ldap:/// today :-)
regards,
Holger
pgpI6LRHs5Y5c.pgp
Description: PGP signature
