Re: Ldap_bind problem with TLS - SDK 5.1.7 and NSS 3.11 & NSPR 4.6.

we probably should place something like "if not inited dont go further"
safeguard in our code but the crash occurs in NSS itself which cannot
handle "not inited" case in some places. if you use DBG build of NSS it
will quit with Assertion failure: mod != NULL, at pk11slot.c:1844 here
http://lxr.mozilla.org/security/source/security/nss/lib/pk11wrap/pk11slot.c#1844
and with OPT build it will carry on and crash somewhere down eventually
.

Mark Smith wrote:
> Anton Bobrov wrote:
>>
>> you need to initialize & configure NSS first. you can do
>> that with one of ldapssl_ init functions [example below].
> 
> It would be better not to crash when no init function is called.  Should 
> we change the libssldap code to fail the start TLS call if NSS has not 
> been initialized?  Is it possible to tell whether NSS has been initialized?
>