Bug 124374 (DEFECT000308637)

Summary: client abends when calling ldapssl_set_verify_callback
Product: [Novell Products] NDS SDK Reporter: Forgotten User WOalQCA2Pj <forgotten_WOalQCA2Pj>
Component: LDAP C SDKAssignee: Forgotten User WOalQCA2Pj <forgotten_WOalQCA2Pj>
Status: VERIFIED FIXED QA Contact: Sundar Swamy <ssundar>
Severity: Critical    
Priority: P5 - None CC: aclark
Version: OCT 2006 NDKKeywords: English
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Component Test Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Rajkumar V 2005-10-10 22:54:45 UTC


------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000308637 at remedy/
remedy/show_bug.cgi?id=DEFECT000308637
Originally filed under the NDS SDK product and LDAP C SDK component.

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> I have a test script which somehow occasionally has a
      NULL context when it calls the function ldapssl_set_verify_callback.
      The client abends with an access error. (dereferrencing a NULL pointer)

SSL_CTX_set_verify(ssl_ctx_st * 0x00000000, int 0x00000001, int (int,
x509_store_ctx_st *)* 0x01a03560 verify_callback(int, x509_store_ctx_st *))
line 1268 + 6 bytes
ldapssl_set_verify_callback(int (void *)* 0x019313ac XpozVerifyCallback(void
*)) line 456 + 18 bytes
LDAPSSLSetVerifyCallback(ParmList * 0x0160e1d0, CommonBase * 0x008b25e0,
Buffer * 0x00000000) line 1669 + 10 bytes
 </remedy_details>
---------
<remedy_notes> rbeauchamp (  7/31/02 11:28:26 AM  Testing -
      Submitter/Final ) Kal there are two problems. 1) Your code
      is calling ldapssl_set_verify_callback after it as done an
      ldapssl_client_deinit. This will have to be fixed in your code. 2) The
      client should not abend and so I have made a fix in ssl_cert.c. This
      has been checked in and should be in the thursday build.

 </remedy_notes>

Comment 1 Forgotten User WOalQCA2Pj 2006-03-14 15:53:45 UTC
unable to reproduce this bug