Bug 172623

Description of problem:
The certifiate verification callback logic in OpenPegasus was only deleting 
the last certificate in the chain.  Please refer to OpenPegasus Bugzilla 4330 
(http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=4330) for details.

The following patch has been submitted to OpenPegasus 2.4.3 and 2.5.1 source 
bases.

Index: SSLContext.cpp
===================================================================
RCS file: /cvs/MSB/pegasus/src/Pegasus/Common/SSLContext.cpp,v
retrieving revision 1.39
diff -r1.39 SSLContext.cpp
286a287,296
>     if (exData->_peerCertificate != NULL) 
>     { 
>         //Delete an existing certificate object from a previous call. 
>         //SSL validates the certificate chain starting with the root CA and 
working down to the peer certificate. 
>         //With this strategy, we end up with the peer certificate as the 
last certificate stored in the SSLCallbackInfo 
>         //so we can retrieve the correct certificate info and username. 
>         delete exData->_peerCertificate; 
>         exData->_peerCertificate = NULL; 
>      }    
> 

Version-Release number of selected component (if applicable):
tog-pegasus-2.4.1-4.4.rhel4 

How reproducible:
Every time.


Steps to Reproduce:
1. Configure the CIM Server as a destination for receiving Indications using 
CIM-XML over HTTPS.
2. Repeatedly send Indications to the targeted CIM Server.
3.

Valgrind can be used to detect this memory leak.
  
Actual results:


Expected results:


Additional info: