RE: nss_ldap feature broken by changes in tls.c (ITS#1555)

["Howard Chu" <hyc@highlandsun.com>]

Unfortunately the man pages are extremely out of date in this area, so
for now the source code must serve as the documentation. That's probably
not the answer you wanted to hear, but that's how things stand today.
The best examples for how to use the libraries are probably in clients/tools,
e.g., ldapsearch.c.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc  
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: Andrew Findlay [mailto:andrew.findlay@skills-1st.co.uk]
> Sent: Friday, January 25, 2002 3:21 AM
> To: hyc@highlandsun.com
> Cc: openldap-bugs@OpenLDAP.org
> Subject: Re: nss_ldap feature broken by changes in tls.c (ITS#1555)
> 
> 
> On Fri, Jan 25, 2002 at 06:48:44AM +0000, hyc@highlandsun.com wrote:
> > Your suggested workaround seems harmless enough, but I think the 
> correct fix is
> > to change nss_ldap to use a NULL association on its call.
> 
> OK - I will report this to the nss_ldap maintainers. It would help to
> have some documentation for the ldap_set_option call to point at, but
> all I have managed to find is the (expired) Internet Draft
> draft-ietf-ldapext-ldap-c-api-04.txt which does not include any
> information on the TLS controls. Is there some reference to OpenLDAP's
> use of TLS somewhere?
> 
> Andrew
> -- 
> -----------------------------------------------------------------------
> |                 From Andrew Findlay, Skills 1st Ltd                 |
> | Consultant in large-scale systems, networks, and directory services |
> |        Andrew.Findlay@skills-1st.co.uk       +44 1628 782565        |
> -----------------------------------------------------------------------
>